Related
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Something similar ....
I had a similar experience on the 15th .... took my N5 off the Qi charger and the screen froze when i tried to unlock it.
I hit the power button and was able to unlock and get a few touches in before it froze again.
I was finally able (after much screen off/on cycles) to get down to the developer options and turn on show touches & show cpu usage.
... background processes looked fairly normal when the screen was frozen(touches showed as frozen) ...
I was rooted, stock rom except for xda user Jishnu Sur's N5 camera mod and running a couple tried & true root apps(Stickmount & QuickBoot). Thought some software issue might be jamming up the digitizer i/o causing it to freeze.
Reverted entirely to stock (the Team Win recovery was also experiencing screen freeze - buttons worked fine) including removing TRWP and re-locking the boot loader!!
The screen freezing problem persists ... my conclusion is that it's a hardware issue. :crying:
It's possible you are seeing the same thing, but I haven't seen anything in the forums to indicate it's a widespread problem.
Returning it for a replacement phone ... :fingers-crossed:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
biggiephat said:
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Click to expand...
Click to collapse
Freezes tend to happen on custom kernels specially if you under-volt it too much. have you done that?
Screen Freeze
canaillou2k5 said:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
Click to expand...
Click to collapse
Last week I had the same problem with my new NEXUS 5. IT’S TOTALLY A HARDWARE ISSUE.
LG products are however not so bad in the JAPAN market but still we are expecting a lot from LG technology.
LG services suck.
I am facing the same problem with my Nexus 5. Unrooted, bought 7 months back from India itself, was working fine till around two weeks back,when the lags, screen freeze, blacking out n all appeared. Got it repaired twice at the LG centre. They changed the front display touchpad as well as the charging connector strip. The problem still persists.
So here's my issue. Yesterday, my phone started to give me a while screen full of dead pixels (pinkish color) randomly. I would turn off the phone, turn it back on and after 2-3 minutes it would crash again. Last year I dropped it and cracked the screen, so to me it was related to that. The phone works fine other than that (music plays when display fails. I did wipe it completely and reinstalled Kit Kat, it solved the issue temporarily but after 30 minutes it started again.
Today I decided to go check out a phone repair shop and ended getting my phone fixed by them. What this consisted of is a replacing the display and plastic frame. I picked up the phone and everything was perfect, new screen and display which looks and feels like new.
Now it's been about 5 hours and the phone started acting strange again. Now it's a lot less worse than before, but I still get the full screen of dead pixels. The display will go on and off (I guess it's trying to reinitialize or something) but always fails. So I end up rebooting the phone for it to work again.
The 2 times it happened after getting the phone fixed it was when I put it in my pocket to go from my work to my car, and then from my car to my home. So I don't know if it has anything to do with being in my pocket, that's why I came here.
So could anyone could shed some light on my issue here? Is my phone already dying? It's only been 13 months and I'd hate to have spent for a new display for basically nothing.
Replace the flex cable. If that doesn't work then it's an issue with the motherboard/screen, in which case you would have to guess between the two, or simply send it to LG and pay for a repair.
I'm not sure how this is possible, but about once or twice a day, the back button on my S6 is pressed on it's own. It has happened when the device has been on the desk, I see the soft keys light up, the device vibrates like they've been touched and the app I was on went back, all while I was not even touching the device.
It's happened mostly when I'm holding the phone but not even close to touching the buttons, and once it happened and pressed the back button about 10 times in a row while I watched it.
The phone is completely undamaged, perfect condition, never touched water, not dirty at all, buttons are 100% clean. Happens while it's charging or on battery.
Has anyone else experienced this?
(My device was repaired by Samsung for a different issue, motherboard replaced, this only started happening after the repair)
i have, started like yours random. then it started happening more and more so when i was at the store waiting for someone i decided to factory reset ( factory reset twice while at the store) but it got worse. couldn't even get passed initial setup the phone just kept spamming back button so i just kept going back. luckily i already ordered a replacement s6 from tmobile since i was having some other issue with the phone. sadly the replacement s6 took over 7 days to get here. shipped through UPS and got to hawaii then for some reason UPS gave it to USPS for delivery. kinda sad that i ordered screen protectors 2 days after i ordered replacement phone and the screen protectors got here 4 days later through USPS. but other than that my NEW ( we all know its refurbished) galaxy s6 so far has no issues. even the no audio on calls is fixed.
also if you are going to order a replacement, be sure to let them know you have a GALAXY S6 and the date it was released. i say this because the 2 tmobile reps i talked to kept asking questions they say it was for them to determine if my galaxy s6 that was what 2 almost 3 months old at the time was still under warranty
My s6 was showing the same issue with the stuck back button.
It started randomly but than it went crazy and stuck. I wasn't even able to use it.
But 1 factory reset fixed it.
But yesterday the random stuck back button started again when the phone was on my desk and it was really hot (weather was hot as well as the phone). I turned it off for a while and apparently the issue stopped.
I'm not sure it's temperature, firmware, whatever related but I really don't want to factory reset it again.
No solution here, but it is happening to me as well
Solved
Hi i had the same problem aswell , i bought samsung s6 in Pakistan, after the update the back button kept pressing ghostly, i went to local samsung repair shop and the assistant reset something from the setting and then it was fine, i even asked him what you did and how you did? but he said it is secret lol very stupid. i could have post the solution if i know it, but i think it is very easy and something to do with setting. i am sure it is not hard/soft reset. i will post this on other forums to help other people.
thanks
having this problem with my phone too, i cant even get it to stay on the settings screen long enough to back up my stuff
edit: well i think i solved it. i tried clearing the cache, didnt work. then i did a hard reset, didnt work. then i went back and cleared the cache and did a hard reset at the same time and it seems to have worked.
+1 same problem. It happens mainly when the phone is on the move. Funny thing it happened 3-4 times while taking the metro (go figure) with the data on. Usually when I turn off the data, it reduces the amount of back press.
Normal reset doesn't solve the problem. It stops after a while, probably when the phone cools down. I can't seem to reproduce it, but I believe it has something to do with the data on.
I don't really want to factory reset so I'm going to write to samsung directly as the phone is brand new.
i am having same issue too.
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
Did anyone try loading a custom rom and got it fixed ?
I've had that issue with my first one. Took it back ASAP as it was DOA. Got a brand new one 3 days later as they didn't have any in stock. This one doesn't have any problems. Don't worry to mutch about it. Get it exchanged.
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
I have the exact same problem...did anyone contact the manufacturer and got a response on the matter?
I believe it may be an app setting messing with the system settings. My device did it once and wouldnt allow me to use my device. After factory reset it made it worse so i used twrp and wiped everything but my modem and flashed my stock firmware and it stopped and hasnt done it since
Sent from my SM-G925P using Tapatalk
faiding said:
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Hum that's interesting, thanks for your precious input on this.
I did contact Samsung who asked me to do a factory reset. It didn't change anything.
They redirected me to a Samsung office in Paris, not for repair but for a deeper factory reset... (not sure what they are talking about), but I haven't been there since due to lack of time.
However, I didn't experience the problem since the last update FXXU3QOKN so I'm keeping an eye on it.
Following "faiding's" comment, I'll probably pay them a visit for a replacement.
working "workaround"
workaround:
lower the speaker volume to ~75% in all settings (Media, ringtone, system, notifications, etc...)
Whats going on? why is it working?
some posts ago someone (user called "faiding") mentioned something about EMC leak, or at least he meant to, by mentioning a faulty insulation.
with that in mind i did some testing and found out that the closes radiating component it the speaker... and once you lower its emissions even thought the faulty insulation, the EMC leak is sufficiently low and the 'capacity short' is avoided.
Note: depending on how 'faulty' is your insulation (it varies from one phone to another depending on production line assembly) lower the volume until the issue stops accruing.
not full-proof but working
What worked for me is turn power saving on
possible fix
might be a coincidence, but this worked for me:
(I am a new user so i cant post a link but here is what you should do)
1. enter YOUTUBE
2. find this video: "Samsung Galaxy S6 Touch Screen Sensitivity Fix"
worked like magic for me
Repair tech
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
dslayer83 said:
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
Click to expand...
Click to collapse
Hi dslayer83,
I've the same problem with my S6
Could you solved the problem replacing the charging port?
It would be very important to me knowing how to repair the phone because I buyed it abroad. In my country Samsung does not cover warranty.
Up with this thread!
I had an S6 since January.. initially the problem was very random, maybe 1 or 2 times per day, sometimes would go crazy for a while
Then i had some time with no defect at all (a couple of weeks?) without doing nothing
This past week, the phone was feeling like the MENU button (what menu as in this phone there isn't any?) and that was very weird!
Today, it simply went completely crazy, and now is completely unusable... i can't actually swtich it off as the back key is pressed so quickly i don't have the chance of doing nothing!
EDIT: Managed to reboot and wipe cache... now it is useable, but still hits the button from time to time
Update... went unuseable again today.... factory resetting now...
If it works, shall we suspect is something software related?
Update: Not working... it started giving the phantom touches just after the factory reset then suddenly stopped
Worked fine for few hours, then started craza again
Now i have done a wipe and factory reset again, and still unuseable
Hi all,
Long story, but the quick version is my home button rarely does anything any more and the screen wakes up by itself from being asleep after anywhere from 3 seconds to 12 seconds.
Now for the long version:
Non-rooted Galaxy S6, by the way. I did a factory reset last week, just because things were getting sluggish. It went well, things were back to speed, and I reinstalled the essentials I wanted. Last night I noticed my phone kept waking itself up over and over again. Then I noticed the home button wasn't doing anything. I rebooted it and it didn't change a thing. After a little more time, the power button also stopped responding. I couldn't even do an emergency reboot with those two buttons disabled. I even tried sticking it in the freezer for a few minutes to see if it was too hot. Google told me about the on screen menu thing to emulate the softkeys so I was able to use that to get around and do reboots.
I hadn't installed any new apps in the last 24 hours, but what the heck, I did another factory reset. I had the option to restore all the apps and settings from 1 day ago, so I chose that. The problem still was there. Dang it, I thought I should not have restored those apps, so I did another reset, this time a totally clean one. The problem not only still happened after the reset, it was doing it during the reset, if the screen went to sleep during a step in the factory reset, the glitch would wake it back up in a few seconds.
I decided last night to just turn it off and charge it fully and hit the Sprint store in the morning. Oddly while charging with the phone powered off, the green battery display would go off and on the whole time it charged.
In the morning I turned the phone on....and NO problems. (of course) For 2 hours not one glitch. So just before leaving for work it starts happening again. Another factory reset at work and a system update from Samsung and still, the problems are there.
I'm just thinking I'll hit the Sprint store tomorrow and swap it out for a new one...but I thought I would tap you guys for any info if you had any.
Thanks in advance, Larry
Sounds like your phone got wet. Factory reset over and over again will not fix this problem ha
Hi,
It seems like a problem with the hardware itself. So yeah, factory resetting all times won't help. Go get a new one .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
Try to use this method
http://forum.xda-developers.com/showthread.php?p=62872996
_______________________________________
thereassaad
XDA Assist
Thanks for the ideas, I tried the dialer thing, thereassaad, but it didn't help. It does sound like water damage, but there is no way. I've never dropped it or been near any water. I'm heading to the Sprint store tomorrow, too busy today. I'll let you folks know how it went tomorrow night.
Just FYI, they replaced the screen saying that fixed the home button not responding and the screen waking itself up, but said I probably shouldn't restore with my google account, since it's likely corrupting my system... Huh? I said. They said the hardware was fixed, but I should create a new google account. I said no way. I said what does having just my contacts imported (no apps) have to do with hardware failure. I said, open up a new phone and lets put my google account on it and see if it breaks the new phone, they said no.
In the store we added my google account to my "fixed" phone with the new screen and all and it messed up again. They said, never mind, we'll replace it, and it should be there this Tuesday.
I didn't ask if it would be a refurb, but I really don't care as long as it works.
So that's my story. So far.
They swapped it out for a new phone, refurb likely, but I'm not sure how to find that out. (not that I care too much) I'm loving the new phone, it's like unboxing day again. No cost out of pocket for me too, which is nice.
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
This happened to my wife's Pixel 7 the first morning she had an alarm set with it.
Did you by any chance snooze it half a dozen times? It was only after she refused to get up that it locked. I think maybe it's a feature, not a bug.
That sounds familiar as if it might've happened once on my OG Pixel years ago, but I can't say for sure.
rczrider said:
It was only after she refused to get up that it locked. I think maybe it's a feature, not a bug.
Click to expand...
Click to collapse
LOL! Good point.
No snoozing and it just locked up for the second time just now. The time is displayed but stuck at 8:16 and it currently 9:57, never had this issue on the 6. I'm wondering if I have bad RAM or something that is causing random lockups.
I do see that it vibrates when I press and hold the power button but I can't see what it's doing with the screen locked up.
Talking to support, they wanted the IMEI number and a picture of the screen? The screen looks normal but is locked up. ???
They have to put me on hold to talk to someone else for each part of the questions. I called Google support but it sounds like someone overseas.
I don't see what they can do, other than replace it. I copied everything from the old phone that was working fine.
They want me to back it up and do a factory reset. I just did that when I got the phone a few weeks ago.
Then they asked that I run the phone in safe mode for a few weeks to see if its a bad app that was installed.
I asked to speak with someone more knowledgeable and they needed to put me on hold again saying I could get an email from someone or wait to talk with someone. They then said I had to give consent for them to look at all my data. ??? After the long hold I was told that I'd be getting an email. Total waste of time.
My screen froze and became unresponsive when I swiped down for notifications while watching non-fullscreen video on Youtube TV. The audio continued to play. I recovered by holding down the power button for 60 seconds to force a reboot. I can't duplicate it though.
I have had these screen freezings too. By pressing power button for 30 sec it boots the phone back up. Then after a minute or an hour it happens again. Had to do factory reset two times already. That's the only thing that helps.
I have no idea of what is causing that.
Mine has done it three times now, had to power cycle it as mentioned above, and each time it was a different app
Here is their suggested fix:
Here are some additional steps to take to try to resolve the issue with your Pixel phone:
Troubleshoot your apps
Perform a factory reset
After each step, check to see if your issue is resolved. If not, continue to the next section.
Tanquen said:
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
Click to expand...
Click to collapse
SystemUI has crashed a few times on mine, which causes a lockup. Rebooting seems to fix it, for the most part.
Tanquen said:
Here is their suggested fix:
Here are some additional steps to take to try to resolve the issue with your Pixel phone:
Troubleshoot your apps
Perform a factory reset
After each step, check to see if your issue is resolved. If not, continue to the next section.
Click to expand...
Click to collapse
You can report back that the factory reset fixes the bug for a while. But if I have to do a factory reset every week, I'm going crazy.
miimaa said:
You can report back that the factory reset fixes the bug for a while. But if I have to do a factory reset every week, I'm going crazy.
Click to expand...
Click to collapse
Just rebooting the phone fixes it for a little while. That's the trouble with random inconsistent issues. It could take a week or two or more for it to do it again. With a number of others having similar issues I don't think a factory reset again is going to do anything. I just got the phone a month or so ago and it was at factory default. What good would it do to put it back to factory again? Sounds just as unreasonable as using my phone for several weeks in safe mode to see if it's another program causing the problem.
Woke up this morning and the phone had rebooted.
RMA your device keep trying until you get someone that understands your issue. Google support is absolute rubbish and if the rep doesn't understand that you're losing all touch input just hang up and try again. It's frustrating but it's sadly the only way you'll be able to get your phone swapped out. I had this problem on my P6P and only a RMA solved my problem.
They offered to let me send it in and let their techs look at it for 2-3 weeks or take it to a local shop. I was surprised that there was an authorized shop in my city but what are they going to do with a phone that reboots every 5 or 6 days? I've not even had it 30 days but they said it was too long just be able to return it. You have 15 days. I pushed back and they set up a replacement but not before telling me about the option to mail it in a wait a few weeks. Who can be without their phone for a few weeks. I have to buy a new one and then have 30 days to return this one.
I do wonder if it's a software issue that Google will fix at some point but don't think so. There is a thread on their support forum that has not been locked yet with a number of folks with what sounds like the same issue.
Oh wait it's 21 days to return it.
"Remember that if we don’t receive your old item 21 days after your replacement ships, you will be charged $968.67, which is the full value of your replacement item."
Tanquen said:
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
Click to expand...
Click to collapse
I would attribute it to buggy software. My 7 pro locked up about a week into ownership. The last time I had a phone lock up was my last pixel phone (the 3). Not sure what it is but it always clears up after a couple updates. Maybe the same will happen for you.
Tanquen said:
They offered to let me send it in and let their techs look at it for 2-3 weeks or take it to a local shop. I was surprised that there was an authorized shop in my city but what are they going to do with a phone that reboots every 5 or 6 days? I've not even had it 30 days but they said it was too long just be able to return it. You have 15 days. I pushed back and they set up a replacement but not before telling me about the option to mail it in a wait a few weeks. Who can be without their phone for a few weeks. I have to buy a new one and then have 30 days to return this one.
I do wonder if it's a software issue that Google will fix at some point but don't think so. There is a thread on their support forum that has not been locked yet with a number of folks with what sounds like the same issue.
Click to expand...
Click to collapse
I believe it's part of their call flow offering the repair shop or mail in option. There's always the advanced RMA option where they put a hold on a card you provide and the temp charge is removed once they receive the defective device. If you don't want the chance at getting a refurbished replacement do the advanced RMA sooner rather than later.
The phone froze on me 3 times already - 2 times using Samsung browser, 1 time on Chrome.
Android 13 QPR1 Beta 3.1 introduces a GPU fix, which will hopefully resolve this issue:
Fixed issues where a device's GPU drivers sometimes caused the system UI to freeze during normal device use.
I'm swapping it out for a new(?) one. Hopefully all goes well.