Hello and good day all,
I just buy my Samsung Galaxy Note 2 (GT-N7100) for 3 days now.
Straight to the point, I'm having this weird problem where I didn't experience it on my previous Samsung Galaxy Note.
The problem is, my screen freeze whenever I open the phone. (Pressing Home button and then you should either put password or swipe)
The screen doesn't respond to my touch.
I have to Lock it again (Power Button), and Unlock it (Home Button) and then it works like usual.
Another thing is, when I'm on the freeze state, my S-Pen can be use but touch of the screen with fingertips doesn't work at all.
And the Freeze Screen only occur when I let the phone for a moment (Going Locked, Black Screen, more than 5 sec)
By the way, the screen also Freeze whenever there's a call. I cant Swipe the button to answer the call.
Already try this few step but the problem still occur.
1. Restart Phone.
2. Factory Reset.
3. Turning Off Wifi Mode Saver (*#0011#)
4. Turning Off S-Voice.
5. Changing Lock Screen Option (Swipe, Pattern)
6. Removing some of App (Facebook, Instagram)
I think the problem occur since I'm upgrading the Firmware to the latest one via Kies.
Is there anyway to fix this problem?
Seeking for your advice sir.
Anyone?
I also try to clear cache partition at recovery mode.
Still no luck.
Ugh, this is really getting frustrating.
Last night I alrdy reflash my old stock rom with Odin v3.04.
Still, the problem occur.
Read someone post, mentioning that screen protector is disturbing the sensor, yet alrdy remove the screen protector but the problem still persist.
And doing some test, SensorHub Test (#*0*#) and fail.
Alrdy include as a attachment.
Can someone just tell me this is factory faulty so I can claim the warranty......
What's the problem.....
Did you find a fix for this? I'm getting a very similar issue, though with mine when it's locked it won't respond to anything and have to do a battery pull
Nooe. Didn't find any. Already try all solution that I cant find. I think it's a hardware faulty.
Just now I go to the retailer and a good news is I get a 1 to 1 exchange with a new device since the retailer itself didn't found a solution for it.
And my suggestion is bring your device to the retailer where you buy it. Hope they can figure something out.
Tq.
Sent from my GT-N7100 using xda app-developers app
Related
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
i think its just a 4.3 software bug. i love the tablet but the new update isn't very good IMO. google needs to get this right.
luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
Since it has to be new I'd recommend just trading it in for another if a reboot or reset didn't fix it. I'd hate to see a fellow get stuck with an unreliable device. It could be many things though such as a bad digitizer or loose LCD ribbon flex cable or just a software glitch. To check the flex cable you would have to disassemble the unit which of course could potentially cause problems when trading it in. I dropped a tab one time though and it Jared my charge flex cable loose and just reinserting it fixed it. Good luck
fix-this! said:
i think its just a 4.3 software bug. i love the tablet but the new update isn't very good IMO. google needs to get this right.
Click to expand...
Click to collapse
Thanks.
Any idea about how to fix the problem (factory reset did not work) other then sending it back for a replacement?
Wait for Google to release official image then return to stock to see if it fixes it.
conan1600 said:
Since it has to be new I'd recommend just trading it in for another if a reboot or reset didn't fix it. I'd hate to see a fellow get stuck with an unreliable device. It could be many things though such as a bad digitizer or loose LCD ribbon flex cable or just a software glitch. To check the flex cable you would have to disassemble the unit which of course could potentially cause problems when trading it in. I dropped a tab one time though and it Jared my charge flex cable loose and just reinserting it fixed it. Good luck
Click to expand...
Click to collapse
Thanks.
I have a feeling it is a software problem. It was perfectly working and few minutes after it was not. Nothing, hardware-wise happened in the middle.
Software-wise, I noticed, on the top of the screen, the notification that a keyboard update was installed. Could have it broken something?
I thought a factory reset would have handled that possible problem but it did not.
luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
I had the problem last night and a reboot fixed it. Haven't seen the problem since.
mi7chy said:
Wait for Google to release official image then return to stock to see if it fixes it.
Click to expand...
Click to collapse
Mi7chy,
thanks.
A question: I started reading this guide (http://forum.xda-developers.com/showthread.php?t=1907796) to understand how to flash the factory image and I am worried I cannot perform step 1 of the Driver Installation section (I am unable to unlock the lock screen...).
Any suggestion?
Contemplating of returning this back for a replacement...
Thanks!
luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
I was in staples and their floor model had the same problem, I tried to fix it but it just sat there in a frozen state.
I bought a Samsung Glide i927 phone last month in the US, i bought it unlocked as i am from argentine, and i wanted to use it with movistar.
Recently the phone started to crash a lot, by that i mean that the screen starts going white, with horizontal lines and pixels of different colors appearing, then just turn off or restarts itself, only to crash again as soon as it starts an then turns off.
When this happens i try to start the phone and select the shut down option myself to see if the next time it starts it doesnt crash. But sooner or later it happens again.
This problem its happening too often, and not while doing something in particular like running an app or something. Sometimes it crashes just by plugging it to the power adapter, it even shows the white screen with the lines instead of the charging battery image when i charge it while turned off. I have already try to fix it upgrading android or doing a factory reset, but that didnt work.
Anyone have any idea of how to resolve the problem, or if its a hardware malfunction that cant be fixed?
To make things more difficult, as i said earlier im from argentine, and i cant go to AT&T or Samsung to get it fixed or get a replacement. English is not my first language, so please forgive my orthographic mistakes.
Thanks
This really sounds like some hardware problem, but to be safe, learn how to use Odin and use it to revert your phone to completely stock condition (cleaner than factory reset).
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
This really sounds like some hardware problem, but to be safe, learn how to use Odin and use it to revert your phone to completely stock condition (cleaner than factory reset).
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
I tried to do that, but the first times when Odin try to reboot the phone it just freezes and i have to unplug it. After many tries it finally finished, but the phone keeps freezing and crashing.
The phone even crashes while turned of and conected to the power adapter.
Do you think that with LiteROM 0.9.0, that might fix this issues?
I've got reboots too, try to disable auto brighness
It helps for me
Sent from my SGH-I927 using xda app-developers app
Power button issue
I am having a similar problem. At first, it just happened on rare occasions. However, today, it started doing it repeatedly. The phone was unusable. I did some checking around, and it appears that the power buttons on Samsung phones are prone to sticking. Some people suggest you actually remove the battery and slam the power button against a table. I wasn't going to do that, because I could just see it doing even more damage. What I did instead was firmly tap the power button repeatedly. It seemed to unstick the power button and allow the phone to function again.
Another alternative is to have the power button replaced, but that might be a hassle.
First of all, sorry for my bad english.
I bought it on amazon a few days ago, I have the same problem...
I thing aznemesis is right, because my power buttom is very sensitive, in fact, some times, when I press the button smooth and fast, to turn off the display like, the typical menu appears as if I had pressed the button for much longer period. Which proves your theory. The problem is if I hit the button over a table and the button breaks here in Chile do not exist spares of the terminal
Well, I did. I couldn't stand the desire to do so. After nearly 18 hours, the terminal isn't rebooted again.
Panchon1978 said:
I bought a Samsung Glide i927 phone last month in the US, i bought it unlocked as i am from argentine, and i wanted to use it with movistar.
Recently the phone started to crash a lot, by that i mean that the screen starts going white, with horizontal lines and pixels of different colors appearing, then just turn off or restarts itself, only to crash again as soon as it starts an then turns off.
When this happens i try to start the phone and select the shut down option myself to see if the next time it starts it doesnt crash. But sooner or later it happens again.
This problem its happening too often, and not while doing something in particular like running an app or something. Sometimes it crashes just by plugging it to the power adapter, it even shows the white screen with the lines instead of the charging battery image when i charge it while turned off. I have already try to fix it upgrading android or doing a factory reset, but that didnt work.
Anyone have any idea of how to resolve the problem, or if its a hardware malfunction that cant be fixed?
To make things more difficult, as i said earlier im from argentine, and i cant go to AT&T or Samsung to get it fixed or get a replacement. English is not my first language, so please forgive my orthographic mistakes.
Thanks
Click to expand...
Click to collapse
The horizontal lines on the screen sound as if it is an overheating issue. What were you doing before your phone shut off? Are you using the factory charger?
cure found
take the battery out...blow on the power button with some compressed gas to get the dust out....then pour a drop of silicone based lubricant on the power button so that most of it gets in the gaps...then hit the power button a few times....haven't had any reboots since then
Has anyone else had an issue where the lock screen is unresponsive after you turn it back on? Here's the scenario:
1. Using tablet.
2. Let the screen time out normally or press the power button to turn off the screen.
3. Wake the tablet either with power or home buttons.
4. Screen is completely non responsive. Doesn't register any of my touches on the screen. Have to power off and on the screen multiple times before it allows me to unlock the screen. Orientation doesn't seem to matter.
I have a brand new WiFi only edition, model P600. I immediately did the three small OTA updates Samsung pushed to me as soon as I first turned the tablet on, but I'm pretty sure it was happening before, as well.
Anyone else? Haven't seen mention of this issue here so far.
Sent from my SM-P600 using xda app-developers app
SportingChap said:
Has anyone else had an issue where the lock screen is unresponsive after you turn it back on? Here's the scenario:
1. Using tablet.
2. Let the screen time out normally or press the power button to turn off the screen.
3. Wake the tablet either with power or home buttons.
4. Screen is completely non responsive. Doesn't register any of my touches on the screen. Have to power off and on the screen multiple times before it allows me to unlock the screen. Orientation doesn't seem to matter.
I have a brand new WiFi only edition, model P600. I immediately did the three small OTA updates Samsung pushed to me as soon as I first turned the tablet on, but I'm pretty sure it was happening before, as well.
Anyone else? Haven't seen mention of this issue here so far.
Sent from my SM-P600 using xda app-developers app
Click to expand...
Click to collapse
Never had this problem on my Note 10.1
Yours could be a just a software issue - Try doing a factory reset and see if its anyway better if not then go back and get it exchanged.
P.S I have had this issue just recently on my S3 and this was after doing a recent update (which then got cancelled due to it causing lag and errors on peoples S3's) so I just need to find the time to factory reset it and all should be good (in theory)
Geordie Affy said:
Never had this problem on my Note 10.1
Yours could be a just a software issue - Try doing a factory reset and see if its anyway better if not then go back and get it exchanged.
P.S I have had this issue just recently on my S3 and this was after doing a recent update (which then got cancelled due to it causing lag and errors on peoples S3's) so I just need to find the time to factory reset it and all should be good (in theory)
Click to expand...
Click to collapse
Yeah, I was afraid of that. No joy on the factory reset. I'm rooted and so the Knox stuff is tripped and shows "modified." Hope that doesn't come back to bite me. (Btw, issue was apparent from first boot - before I rooted.) I'm about to go find the factory firmware and ODIN it back on here so at least there's no trace of SuperSU and all the bloatware is back. I think my parents got the Note from Amazon, so hopefully they won't look too closely anyway.
Thanks for the reply.
FWIW, I've tried factory reset, flashing firmware straight from Kies (UEUBMK1), turning off Smart Stay, Palm motion, Reading mode, and I'm the only user registered on the device. No joy on anything. Just going to have to send it back to Amazon for replacement.
Have you tried disabling Daynote?
I've found that when I freeze Daynote the magnetic sensor from eg the book cover case don't work anymore.
My train of thought is that maybe your magnet sensor is defective and Daynote ends up in an endless loop?
meks007 said:
Have you tried disabling Daynote?
I've found that when I freeze Daynote the magnetic sensor from eg the book cover case don't work anymore.
My train of thought is that maybe your magnet sensor is defective and Daynote ends up in an endless loop?
Click to expand...
Click to collapse
Have not tried this, but now it's too late as we've boxed it for shipping back to Amazon. Thanks for the response, though!
Screen not automatically turning off after inactivity, & cant change apps during call
Hi all, so I have the 4GB RAM 64GB storage version of the North American Zenfone 2. Everything has been fine ever since I got it back in May but since yesterday I noticed an issue with the screen not turning off unless I hit the power button. The screen stays on until I use the power button. I can't figure out if it's an app that's causing this or what's happening. I've uninstalled the one app that I've updated since I've noticed this happening but the issue is still there. I have my phone set to automatically turn off after 30 seconds of inactivity and have gone there a few times since yesterday to make sure the setting was correct; screen still stays on. I have just installed Wakelocker Detector Free to see if anything can be found, nothing thus far.
I've also noticed since yesterday that during a call, I can no longer be attempting to use another app (ie. Chrome, Facebook) during the call. What happens is that I'd press back/return (the hardware key), and then it goes back to my homescreen and I attempt to open another app, which it does but within a second, the call screen pops up. I'll press home or back or whatever to try to get back to another app or screen but again within seconds the phone forcibly has the call screen come up again. Previous to yesterday, I would have no issue going on Google Maps, Facebook, any other app during a call but since then these issues have arisen.
Hey I've been having this issue too over the last week. Not quite sure what the issue is. I'll be opening my phone tonight to check if there is a loose cable or something.
Please try booting in safe mode to see if there is a 3rd party app causing the issue:
http://www.asus.com/us/support/FAQ/1005163/
Sincerely,
ASUS_USA
So an update...I sent in my phone to have my screen replaced because I noticed my home button and recent apps buttons were intermittently not working. So I got my phone back today from the repair centre, I've noticed the issue of not being able to switch apps still arising along with the screen not turning off by itself (I have it set at sleep after 30 seconds of inactivity). The home button and recent apps has been dealt with though but the rest of the original problems I mentioned before are still there.
zacxzac said:
Hey I've been having this issue too over the last week. Not quite sure what the issue is. I'll be opening my phone tonight to check if there is a loose cable or something.
Click to expand...
Click to collapse
Sorry, just noticed I finally got a reply in this thread until now. Did you do a check of your own phone and see any issues causing this?
Asus_USA said:
Please try booting in safe mode to see if there is a 3rd party app causing the issue:
http://www.asus.com/us/support/FAQ/1005163/
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
After I get into Safe Mode, what do I do? Do I purposely leave the phone and try to see if the phone's screen turns off by itself?
EDIT: Went into Safe Mode, unlocked the phone and just let it sit there. Screen did not turn off until I pressed power button.
Asus_USA said:
Please try booting in safe mode to see if there is a 3rd party app causing the issue:
http://www.asus.com/us/support/FAQ/1005163/
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
Bump....so anything else you can suggest? Took it in to a repair centre (the same one that did my screen repair) and they said they're gonna try and do an OS reset to see if that's the issue, which I could do myself but I want them to see it themselves and then if there's any hardware that needs to be fixed they can deal with it as well.
I think its a hardware problem, maybe your reed switch or magnetic sensor got damage. This switch turns on or off your screen when a flip cover is installed. To diagnose try to enable asus cover in settings. If your screen turns off and on repeatedly then probably that the reason why youre phone keeps awake. Just bring to a service center, at least you know the problem.
Ice.
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.