Related
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
Hello, as I said in the thread title i have a problem with the screen lock after waking up the phone. It remains stuck, until i push the power button again to close the screen, and then it's working like it should. The problem appears one at 6 or 7 times i wake the phone.
I have tried to change the screen lock method, but i get the same problem, with the pattern activated.
I have also changed two roms, so I guess this is not the issue. It is more likely that an app is the cause of this, but i have the same apps as I had on my Galaxy Nexus, so it is difficult to figure out what is the app causing this. I have paranoid android with franco kernel.
Does anyone have a clue about what the problem could be?
neinfricatu said:
Hello, as I said in the thread title i have a problem with the screen lock after waking up the phone. It remains stuck, until i push the power button again to close the screen, and then it's working like it should. The problem appears one at 6 or 7 times i wake the phone.
I have tried to change the screen lock method, but i get the same problem, with the pattern activated.
I have also changed two roms, so I guess this is not the issue. It is more likely that an app is the cause of this, but i have the same apps as I had on my Galaxy Nexus, so it is difficult to figure out what is the app causing this. I have paranoid android with franco kernel.
Does anyone have a clue about what the problem could be?
Click to expand...
Click to collapse
Hi,
Please tell me if I have well understand :
When your phone is in standby mode (screen off) and you push power button, the screen lock appear but you can't unlock it ?
That mean the screen doesn't respond some time (1 to 6-7) after wake-up the phone ?
I don't know why but I want to ask you if you have under-volted your phone ?
-JFK- said:
Hi,
Please tell me if I have well understand :
When your phone is in standby mode (screen off) and you push power button, the screen lock appear but you can't unlock it ?
That mean the screen doesn't respond some time (1 to 6-7) after wake-up the phone ?
I don't know why but I want to ask you if you have under-volted your phone ?
Click to expand...
Click to collapse
Hi, you have understand well, that is the problem i am facing. It becomes unresponsive quite often.
No, i did not change anything regarding the cpu, nor the settings in franco kernel.
neinfricatu said:
Hi, you have understand well, that is the problem i am facing. It becomes unresponsive quite often.
No, i did not change anything regarding the cpu, nor the settings in franco kernel.
Click to expand...
Click to collapse
That's strange, I have the same settings as you (PA + Franco) without any problems.
I know that Franco's Kernels are great but this is the way that I should follow to try to found the problem.
Do a full wipe and re-install PA + PA Gapp.
Don't install Franco Kernel right now and do the test with PA stock kernel.
If the test is OK, the problem come from Franco's kernel -> ask in Franco's thread
If the problem is still there -> ask in PA thread
You haven't any other problem with your touch screen ? Only with the lock screen ?
-JFK- said:
Hi,
Please tell me if I have well understand :
When your phone is in standby mode (screen off) and you push power button, the screen lock appear but you can't unlock it ?
That mean the screen doesn't respond some time (1 to 6-7) after wake-up the phone ?
I don't know why but I want to ask you if you have under-volted your phone ?
Click to expand...
Click to collapse
-JFK- said:
That's strange, I have the same settings as you (PA + Franco) without any problems.
I know that Franco's Kernels are great but this is the way that I should follow to try to found the problem.
Do a full wipe and re-install PA + PA Gapp.
Don't install Franco Kernel right now and do the test with PA stock kernel.
If the test is OK, the problem come from Franco's kernel -> ask in Franco's thread
If the problem is still there -> ask in PA thread
You haven't any other problem with your touch screen ? Only with the lock screen ?
Click to expand...
Click to collapse
Thank you, i will try the stock kernel, as I only tried franco's.
Nop, no other problem with the screen, only this one with the lock screen, and it is becoming annoying
neinfricatu said:
Thank you, i will try the stock kernel, as I only tried franco's.
Nop, no other problem with the screen, only this one with the lock screen, and it is becoming annoying
Click to expand...
Click to collapse
OK, let's go for a full wipe, I'm sure it will solve the problem.
-JFK- said:
OK, let's go for a full wipe, I'm sure it will solve the problem.
Click to expand...
Click to collapse
Hmmm, that is highly unlikely, as PA is the second rom i have tried, with rasbelly i had the same problem.
I am now trying the stock kernel.
neinfricatu said:
Hmmm, that is highly unlikely, as PA is the second rom i have tried, with rasbelly i had the same problem.
I am now trying the stock kernel.
Click to expand...
Click to collapse
Any news after the FULL wipe ?
-JFK- said:
Any news after the FULL wipe ?
Click to expand...
Click to collapse
I have flashed the stock kernel, for a while it seemed to work better, but 5 minutes ago the screen lock remained stuck again.
I have made a full wipe for the instalation of PA coming from rasbelly, one week ago, still the same problem. As I said, i am almost sure that the problem is caused by an app, but it is quite difficult to see which app is causing this....
screen unlock
Hey I had a similar problem. Do you have Lightflow installed? When I had stock everything, enabling additional LEDs including the LCD backlight had no issues. But apparently with PA and Franco kernel it switches off backlight when you unlock screen. Light flow switches it off. Try disabling that control of LCD backlight maybe? That worked for me
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Obscure Reference said:
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Click to expand...
Click to collapse
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
fivecheebs said:
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
Click to expand...
Click to collapse
Yeah, I know.. I had it built in while running CM. Just had an urge to go back to stock for a while and was just wondering what features I wanted actually required root (and xposed).
If anyone else knows of a way, please let us know.
Hi gys, slightly different issue here, but would appreciate any help.
basically the PIN lock does not activate until 30 seconds or so after the phone boots up. So there is no securuty on initial boot up.
Its there if I do a reboot. But not there if I do a startup from fully off.
It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result and have tried several roms.,
Currently running the latest Chroma rom with the stock kernel. The little circle that's supposed to show up around the lock icon at the bottom doesn't show up 90% of the time (http://prntscr.com/abhku3). I'm trying to unlock it with a bluetooth (not NFC) fitness band.
This isn't a problem with the band, because I tried putting Face Unlock as well, but the detection doesn't show up most of the time.
Is there any way to fix this?
sixaxis94 said:
Currently running the latest Chroma rom with the stock kernel. The little circle that's supposed to show up around the lock icon at the bottom doesn't show up 90% of the time (http://prntscr.com/abhku3). I'm trying to unlock it with a bluetooth (not NFC) fitness band.
This isn't a problem with the band, because I tried putting Face Unlock as well, but the detection doesn't show up most of the time.
Is there any way to fix this?
Click to expand...
Click to collapse
I haven't had an issue with smart unlock before, I pair it with my Moto 360. I don't know if it's the kernel because I personally use the Taurus kernel and not the stock one, that might be a reason but again I don't know for sure at all. Maybe on Multirom I'll install a second Chroma and leave it on stock and see if I can get it to reproduce what you're having, I'll get back to you in about 20-30 minutes on how it goes.
-Edit- Might be a bit longer since I need to redownload the latest build. My internet can be slow at times
-Edit 2- I haven't had the issue, at least with my watch. Not too sure how much further I could help you :/
fireball0093 said:
I haven't had an issue with smart unlock before, I pair it with my Moto 360. I don't know if it's the kernel because I personally use the Taurus kernel and not the stock one, that might be a reason but again I don't know for sure at all. Maybe on Multirom I'll install a second Chroma and leave it on stock and see if I can get it to reproduce what you're having, I'll get back to you in about 20-30 minutes on how it goes.
-Edit- Might be a bit longer since I need to redownload the latest build. My internet can be slow at times
-Edit 2- I haven't had the issue, at least with my watch. Not too sure how much further I could help you :/
Click to expand...
Click to collapse
Thanks for helping out! I tried with the Quanta v10 kernel but had the same problem. Reinstalled the rom. No dice :/
This is strange
sixaxis94 said:
Thanks for helping out! I tried with the Quanta v10 kernel but had the same problem. Reinstalled the rom. No dice :/
This is strange
Click to expand...
Click to collapse
It is a bit strange. I do have one final thing to test out actually. I just remembered my girlfriend got a generic bluetooth fitness band thing for her senior year, I'll charge that up and see if that gives the same issue since I still have the multirom boot with it. It'll take probably an hour to charge it since it's just a generic one.
fireball0093 said:
It is a bit strange. I do have one final thing to test out actually. I just remembered my girlfriend got a generic bluetooth fitness band thing for her senior year, I'll charge that up and see if that gives the same issue since I still have the multirom boot with it. It'll take probably an hour to charge it since it's just a generic one.
Click to expand...
Click to collapse
I'm certain it's not the band's fault cause gave unlock isn't detected either. I'll try the pure nexus and cm roms to see if it makes a difference.
sixaxis94 said:
I'm certain it's not the band's fault cause gave unlock isn't detected either. I'll try the pure nexus and cm roms to see if it makes a difference.
Click to expand...
Click to collapse
Especially if the band was working fine on other roms or devices. CM 13 is my main daily driver rom and I haven't had a single issue with several bluetooth devices I own, I always will recommend it xD The fitness band is almost charged and I'll test that out here real soon
fireball0093 said:
Especially if the band was working fine on other roms or devices. CM 13 is my main daily driver rom and I haven't had a single issue with several bluetooth devices I own, I always will recommend it xD The fitness band is almost charged and I'll test that out here real soon
Click to expand...
Click to collapse
I only got the band 2 days ago and have just tested it on Chroma.
Quick question, does CM13 support Volume Key to unlock AND double tap status/nav bar to lock? My power button is screwed up and it barely registers. Also, are the latest nightlies stable or should I go with an older build, if I don't plan to update my rom in the next month?
sixaxis94 said:
I only got the band 2 days ago and have just tested it on Chroma.
Quick question, does CM13 support Volume Key to unlock AND double tap status/nav bar to lock? My power button is screwed up and it barely registers. Also, are the latest nightlies stable or should I go with an older build, if I don't plan to update my rom in the next month?
Click to expand...
Click to collapse
Double tap to sleep, yes. Let me quick boot into it to make sure for the volume key. If you get Kernel Auditor and the right kernel you can have double tap to wake which is wonderful. Ok it does have the option for volume key unlock. I haven't had any issues with the nightlies, a while back I had one that would randomly freeze my touchscreen but that was early last month.
fireball0093 said:
Double tap to sleep, yes. Let me quick boot into it to make sure for the volume key. If you get Kernel Auditor and the right kernel you can have double tap to wake which is wonderful. Ok it does have the option for volume key unlock. I haven't had any issues with the nightlies, a while back I had one that would randomly freeze my touchscreen but that was early last month.
Click to expand...
Click to collapse
Sweet, I'll give CM a shot! I hope the smart unlock was a rom problem and not a hardware one. My phone's nearing the end of it's life, so it's more than possible.
sixaxis94 said:
Sweet, I'll give CM a shot! I hope the smart unlock was a rom problem and not a hardware one. My phone's nearing the end of it's life, so it's more than possible.
Click to expand...
Click to collapse
How's CM holding up for you? Is Smartunlock working on it at all?
fireball0093 said:
How's CM holding up for you? Is Smartunlock working on it at all?
Click to expand...
Click to collapse
I haven't gotten around to it yet. I'll try it later this week and report back
fireball0093 said:
How's CM holding up for you? Is Smartunlock working on it at all?
Click to expand...
Click to collapse
It was a problem with Chroma. I'm running CM now and the Smart Lock works flawlessly!
sixaxis94 said:
It was a problem with Chroma. I'm running CM now and the Smart Lock works flawlessly!
Click to expand...
Click to collapse
Glad to hear it's working! I've been having some issues on Marshmallow in general lately, contacts aren't syncing from Google. But, I'm gonna open up my own help thread for that xD
youtu.be/wbqOni008hc
Any solutions? I want to know is it software or hardware problem?
edit: Specs
Marshmallow 6.0.1 G900HXXSACQAA/G900HOJP1CPL1/G900HXXU1CPCA
Smart Launcher Pro 3.16.06PX
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Seems to be a standard problem. I have it too.
Internet forums are full of this problem.
Buy another phone than Samsung.
fgth90 said:
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Click to expand...
Click to collapse
I've seeb it alot actually. I mean the wake up problem. But noone seems to fix it yet. If anyone did please tell me
Has anyone test this with older Android 5?
The "Weird" Screen in Low Brightness is AMOLED Burn-in due to intensive use, My S5 Have this problem too.
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Thank you for all the answers guys.
Valmerost said:
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Click to expand...
Click to collapse
Just changed:
Force GPU rendering : on
Disable hardware overlays: on
edit1:it's better than before. I will feedback later. Also gonna try that camera trick
edit2: It's same again. Tried Home2 Shortcut the get the camera trick. It also didn't work because i want my phone to be locked and it doesn't work on locked status
Any other suggestions guys?
what ROM are you guys using? Have you tried a different one?
youdoofus said:
what ROM are you guys using? Have you tried a different one?
Click to expand...
Click to collapse
It's the stock ROM. No, I'm planning to try a new ROM today.
raiwulf said:
It's the stock ROM. No, I'm planning to try a new ROM today.
Click to expand...
Click to collapse
that would be a good place to start
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
raiwulf said:
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
Click to expand...
Click to collapse
if thats the case, then it might be a hardware issue
this is weird af, tons of people have this issue, no solutions yet
raiwulf said:
this is weird af, tons of people have this issue, no solutions yet
Click to expand...
Click to collapse
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
derAndroidler said:
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
Click to expand...
Click to collapse
baaahahahahaha!!! My fiancee has a OnePlus 2 and is a pretty big fan of it. The camera app for samsung TW is far superior tho