Hello all and thanks for looking here into my problem.
My phone runs on the clean and efficient CleanROM 7 with the stock kernel that came with. I've noticed a bit lately that when I pull up my phone and unlocked the lockscreen, the phone black screens and just freezes at that point. Can't do anything with the power button, so I have to hard reset with the battery coming out and back in.
The one thing I've noticed at the lockscreen is the status bar at the top isn't visible. At that point, I just tried to flicker my screen off and on to see if it appears, but it even freezes when I flicker it off. Any suggestions or ideas as to what's going on?
Thanks
Sent from my SCH-I535 using Tapatalk 2
Bump
I've tried searching for a solution too, but I haven't seen one yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
That might be rom related, or specific to certain settings when using one style lock screen over another. Might want to go into settings for lock screen and make sure that ripple effects are turned off. Also might want to ask in the Rom thread itself. Other users may have experienced the same and be able to answer your question.
Sent from the future via Tapatalk 4
Related
Does it seem to anyone else that the screen on this phone doesn't always register input as consistently or quickly as it should?
Is this a software or hardware issue?
Sent from my Nexus S using XDA App
Hog Milanese said:
Does it seem to anyone else that the screen on this phone doesn't always register input as consistently or quickly as it should?
Is this a software or hardware issue?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I'm wondering the same thing. For instance the keyboard seems to have trouble with registering a keypress on the same key that just worked fine the press before. Granted I just got the phone yesterday and I'm in my learning curve, and it's still stock. Lovin my ns4g with no bloat either way ;-)
Sent from my Nexus S 4G using XDA Premium App
I just posted about this. Didn't seem as bad until I rooted the phone, but that was within about three hours of getting it. It's annoying as hell, right? My thread is in the General Forum. ugh.
The screen is definitely not as sensitive as HTC screens. And I agree, it's annoying.
My screen was to sensitive before update but saying HTC has more sensitivity touch screens I beg to differ
Sent from my Nexus S using XDA App
Mine is so sensitive that I don't even have to touch the screen, it will register a touch if I hover just above it.
Sent from my Nexus S 4G using XDA App
what update is this you're referring to?
mine also does the hover thing. I'm getting very annoyed with this...
Sent from my Nexus S 4G using XDA App
I know the feeling, mine seems to be solely limited to the pre-call dialer. On the dialer it works like a 15 year old palm pilot. Everything else is hyper sensitive. It works fine when in a call.
Sent from my Nexus S 4G using XDA Premium App
Is there a setting to change the touchscreen sensitivity on the Nexus S?
I have noticed when the screen is hot it doesn't register keys pressed, I always end up hitting the "." Its quite annoying but j do however love the phone
Sent from my Nexus S using XDA App
Is there somewhere on the phone to set the sensitivity?
Mine falls into the "So sensative that it registers a touch when I hover my finger over it".
Sent from my Nexus S 4G using XDA App
I apologize if I'm a little cranky but no one seems to see my question. Is there ANY SETTING available for the sensitivity of the touchscreen?
floridapossum said:
I apologize if I'm a little cranky but no one seems to see my question. Is there ANY SETTING available for the sensitivity of the touchscreen?
Click to expand...
Click to collapse
No setting that i know of. I believe some kernels adjust sensitivity but its one setting built in not adjustable. I am running netatchy kernel and responsiveness is amazing.
87Octane said:
No setting that i know of. I believe some kernels adjust sensitivity but its one setting built in not adjustable. I am running netatchy kernel and responsiveness is amazing.
Click to expand...
Click to collapse
Yep that is true, sometimes it depends of the ROM or Kernel you have.
Hello, fellow Nexus S owners. I am resurrecting the thread because I found myself in a similar situation.
But first some history and details - I own a I9023 handset and have been using stock ROM since it came out (JZO54K). Couple of days ago I noticed that the lower part of the screen (the line right above the hardware buttons) is less responsive and sometimes even unresponsive. This makes it really annoying when trying to call somebody and nothing happens when I try to launch the dialer. The same behavior is observed throughout the whole row this includes even applications button. When texting the same things happens.
At first I thought that this could be due to me installing a "Temple Run" kind of game, but I wiped it, rebooted and the problem remains.
What do you think? Could this be a hardware problem or software one?
Your digitizer might be dying.
It's also known that while charging the phone with the wrong charger the screen goes crazy, but then, unplugging the phone will usually solve the issue.
Envoyé depuis mon Nexus S avec Tapatalk
BenHeng said:
Your digitizer might be dying.
It's also known that while charging the phone with the wrong charger the screen goes crazy, but then, unplugging the phone will usually solve the issue.
Envoyé depuis mon Nexus S avec Tapatalk
Click to expand...
Click to collapse
Luckily the device is still under warranty so I will take it to my vendor for repair. Maybe then I will have some info on what's happening.
I had a similar problem a while back when my battery started to die. I've never experienced any touch screen wackiness caused by third-party chargers, but this seemed to be a comparable issue albeit in the opposite direction. So in addition to my battery losing charge real quick touches wouldn't register in the bottom half of the screen.
I've had my Infinity for about a week now and on at least 3 occasions I've had the tablet screen go blank and reboot it self after 10 seconds or so. When this happens the screen usually turns all white or all black and is unresponsive. This has happened on firmware 22 and 26. Anyone else experiencing this?
Sent from my ASUS Transformer Pad TF700T using xda premium
I have experienced this twice. It happened to me last night in fact. I hit the back button to go back in the XDA app and it went all white. I had to hold the power button for a few seconds before it would reset though.
Sent from my Transformer Infinity!
Do you have an NTFS-formatted micro SDHC in it by any chance?
I've had this happen many times mainly while switching apps... Usually between games to normal apps like email... I have mine completely stock without any sd card...
Sent from my ASUS Transformer Pad TF700T
Happend with my tab too. But only with games so I supposed they are not perfectly adapted to the Chip and thus crashing it or the other way round.
This has happened without any sd card present. Tab is completely stock, not rooted and it is always between apps.
Sent from my SAMSUNG-SGH-I747 using xda premium
possibly the task manager
Did a little searching and found someone having a similar problem here http://forum.xda-developers.com/showthread.php?t=1523487. I've been having the screen go out sometimes and it reboots, other times nothing on my bootloader shows up and it's just my background wallpaper.
Someone suggested that it was due to the the task manager widget. I can confirm that I've been running this widget. If this is a common factor among all of us then maybe we have our culprit.
Edit: I don't have a microsd inserted.
This has also happened to me a few times and I'm also using the Asus task manager widget. I'll try removing it now to see if that works.
Sent from my ASUS Transformer Pad TF700T
Same problem here
Usually happens when I'm mass transfering files and doing something else
Will try to remove widget
Edit:
Removed widget and used heavily for a few hours
no black screen/reboot
This happens to me too while playing scramble with friends.
ali4ek said:
Do you have an NTFS-formatted micro SDHC in it by any chance?
Click to expand...
Click to collapse
I do not have a micro SD inserted.
GCq1w2e3 said:
Someone suggested that it was due to the the task manager widget. I can confirm that I've been running this widget. If this is a common factor among all of us then maybe we have our culprit.
Click to expand...
Click to collapse
I do not use that widget and I have still gotten the restarts.
Sent from my Transformer Infinity!
I sent mine back because of this exact problem... happened four times going to black (only settings icon and text showed) and once to white on .22 and .26 update. New tab arrives today... Hopefully all is good this time.
~zealouz
Asus tf700
Acer a700
HTC Thunderbolt
Samsung Galaxy S3
I get it about every other day of heavy use. I am using the Asus task manager widget.
Last time it happened I had been actively checking my screen on time to contribute to a battery thread and noticed my timer lost about 20 minutes of time after the reboot, FWIW.
Hey there,
Just curious if anyone else sees this problem? And if there's a known reason or fix? Pretty much like the topic name says.... sometimes tapping the clock just does nothing, no matter how deliberately I tap or hold it. I know it isn't hardware because when I rotate into the other other orientation, that portion of the screen that was just the clock now responds fine to touch. A reboot will fix. Thoughts?
EDIT: Should have mentioned - bone stock, unrooted, locked etc. Havent gotten up to any tinkering with this thing, too many bad hardware reports to invalidate warranty lol. Though my hardware seems good so far...
Thanks...
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I prefer the ASUS quick setting to stock Android notification, but I don't think I have any problem with them. Have you try cold booting your tablet? Shut down and press power+volume down?
I know you said it's not hardware, yet that sounds like a digitizer problem.
I get this from time to time - I even got it once last night, after flashing CleanRom 2.3... which was a little disappointing.
I've found that if I get a notification of some kind - say, an email being received - it clears this bug and I can then tap on the clock to bring up the quick settings menu and it will work fine from then on. It's only after a reboot that the bug reappears, but then not every time.
Stearmandriver said:
Hey there,
Just curious if anyone else sees this problem? And if there's a known reason or fix? Pretty much like the topic name says.... sometimes tapping the clock just does nothing, no matter how deliberately I tap or hold it. I know it isn't hardware because when I rotate into the other other orientation, that portion of the screen that was just the clock now responds fine to touch. A reboot will fix. Thoughts?
Thanks...
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Yes. I get the issue since I believe JB update. One work around that worked for me is open setting from setting icon, which I have on one of home menu. Some how after that it works again. So I agree it is definitely not related to hardware.
Hi,
Yes, this happens randomly with my tablet too. Likewise, only since JB.
As noted above a notification does seem to make the issue go away. I have tried all sorts to find the cause but always come up blank. Rebooting also removes the problem.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I had this issue with JB. It was annoying as hell. Went back to ICS because of this and the "black flickering lines" problem. I already posted about this, but maybe it was on TF and not here... It's a bug in JB...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
I suffer from this as well.
Yeah, notifications seem to fix it. Glad I'm not the only one... I guess. Really is annoying as hell to not have quick access to brightness settings and stuff. Funny, I didn't know the cold boot required the volume button trick, I thought just a normal shut down / restart did that. Thanks for the tip, I'll do it regularly lol.
Sent from my SPH-D710 using xda app-developers app
Sorry all, but I don't have this issue on my rooted, locked .18 JB. It works very well indeed.
I also have this problem. The only way I can fixitisjust a shutdownand restart. Can be annoying.
Same here... Started after the JB update... One quick fix for me is to plug in my ear-buds and the QSP pops up.. If you don't want to carry around your ear-buds, if you have a pair that you don't use anymore or a damaged pair, you can cut the tip off and carry it around in your case/cover..
Persistantly on screen the little up arrow stays over my home button so I can't use it whatsoever. Sometimes if I reboot it will go away for a short time, otherwise it's always there. I thought it may be from gravitybox but I wasn't sure. Any help would be appreciated!!
Screenshot please
Sent from my Nexus 5 using Tapatalk
Pics
Here ya go! Sorry wouldn't upload earlier
Thanks. Not what I was expecting to see ?
Sent from my Nexus 5 using Tapatalk
Yeah I'm really confused!! any ideas at all?
Sorry not me but hopefully the pic will help someone else
Sent from my Nexus 5 using Tapatalk
Are you using any lock screen mods? I had the issue a couple months ago but forgot how I resolved it.
Sent from my Nexus 5
Weird - even the camera icon on the bottom right is what is usually on the lockscreen (not usually in the app drawer). What mods do you have installed?
I have Notification Mod and Gravitybox
RedEyedChester said:
I have Notification Mod and Gravitybox
Click to expand...
Click to collapse
I have the exact same problem. Glad I'm not the only one who's going crazy with this thing.
I pretty much have your exact same set-up. I disabled Notification Mod last night to see if that is the problem but that damn little arrow keeps popping back up over the home button.
I have no idea how to fix this either.
Same issue... but no resolution...
Honestly it's been so long I don't remember, but somehow I fixed it! I think I red lashed my rom, removing GravityBox beforehand, and reinstalling it, only enabling things I knew I needed. Haven't had issues since. Weird issue though
I'm hoping that this isn't a unique problem just for me but this is literally the first time I've had this problem. Depending on the use of my Note 5 will determine if I can even unlock my phone the next time I turn it on. I'll go about my usual use of any phone should be able to accomplish (browsing Instagram/Facebook/Chrome/Email/Pinterest/etc.). After a little while it become noticeable that the phone is starting to slow down considerably if I continue to use it. However, the one that really grinds my gears is I'll do my typical browsing and then lock my phone, put it back in my pocket. Something we all do, however, the next time I go to pull out my phone I can't even get the screen to come on for sometimes five minutes. I can hear it thinking with random sounds of the lock screen either responding to my fingers touching the screen or the un/lock sound but nothing happens. Sometimes, I can see the screen and all the notifications that I want to check on but nothing is happening. Sometimes, I'll double tap the home button to get to the camera shortcut programmed to it and sometimes the camera app comes up like it should but it is completely unresponsive.
So the steps I've tried to resolve the issue:
Restore to Stock ROM
Different ROMs
Even leaving the Stock ROM alone and just seeing if it still occurs
I'm just not sure what to try next. There's a chance the problem could be a memory error that's occurring physically but I'm not 100% sure.
Attached is my Note 5's current state of customization. Any help with this would be very very much appreciated.
Thank you
Giving a slight bump here. Does no one else have an idea of what c could be wrong?
Sent from my SM-N920T using XDA Free mobile app
CharlieBoy808 said:
Giving a slight bump here. Does no one else have an idea of what c could be wrong?
Sent from my SM-N920T using XDA Free mobile app
Click to expand...
Click to collapse
Have you removed or disabled any system files? Also have you tweaked the kernel in any way?
I will say that I've had issue with v11 of that kernel you are using. I bounce between v4.1 and Sky-high v4.5 depending on what I need my phone for that day.
Sent from my SM-N920T using Tapatalk
I will give those a try. Thank you!
Sent from my SM-N920T using XDA Free mobile app