I don't see any threads about this. I bought the 16 GB c70 model, and sometimes it will, in the middle of using it, just shut the screen off. Sometimes it will come right back on, and sometimes I have to push the power button. Is this an actual issue, or should I not worry about it. Other than that, the only other issue I have random blue lines will *occasionally*(very, very infrequently) show up for a half sec or sec and then disappear. I'm sure if that is a problem, it's the GPU, because it reminds me of something I have seen before. I can't replicate either issue like others can with the "flickering" thing. And I didn't have issues with the screen off issue until I put it in a smartcase, but I can't definitively say it is, or isn't, a cause. Just looking for some advice as to whether I am being picky, like those with the screen flicker, or is it potentially an actual issue in which I should return it within my 14 day return window.
I think I had the same problem
And when I turned my brightness right down the backlight would go off
If you're trying that keep your finger on the slider so you can turn it back up
I took mine back and got a new one, don't have that problem so far
Sent from my HTC Incredible S
Here's the screen issue I'm having. But the model in staples also had the same issue, so I don't necessarily return it for this one unless it is something that will cause greater issues in the long run.
http://www.youtube.com/watch?v=ViTNmS_L85I&feature=youtube_gdata_player
Sent from my Nexus 7 using Tapatalk 2
markj338 said:
I think I had the same problem
And when I turned my brightness right down the backlight would go off
If you're trying that keep your finger on the slider so you can turn it back up
I took mine back and got a new one, don't have that problem so far
Sent from my HTC Incredible S
Click to expand...
Click to collapse
Markj, I appreciate the response, I may do that. I'm going to give it another few days, as I have until 7 days after Tuesday to return it. But it's not looking promising at this point
https://www.youtube.com/watch?v=GefaUMxjUeA&feature=youtube_gdata_player
This is issue I have been having that I described above. It got so bad today that I had time to take a video of the issue.
Related
Okay I've been having this issue since I got my Nexus a couple of weeks ago. Several times a day I'll go to take it out of my pocket or pick it up off a table and when I go to hit the unlock button at the top nothing happens, the screen never wakes up. The trackball will still be lighting up as always but nothing on the screen. I have to pull the battery in order to get it to reboot so I can use it.
Due to this issue and getting dust under my screen I called HTC for a replacement. I got my replacement yesterday and got it all set up again. Within the first 2 hours I picked it up off my table and it wouldn't wake up. And this has probably 4 times since I got the phone yesterday.
Is ANYONE have this issue? I think it's a little weird it happened on my original device and now on my replacement.
Never happened to mine so far that I have noticed. Not that this information helps you any but...
ive bought 2 for me and one for a friend. None have any issues at all so far
I haven't had this problem...
just for the hell of it have you tried restoring it.
DMaverick50 said:
ive bought 2 for me and one for a friend. None have any issues at all so far
Click to expand...
Click to collapse
you bought 2 for yourself and one for your friend? Can I be your friend?
Maybe you're just not pushing the button hard enough, or you need to find a "sweet spot."
I've never had this issue. Is it possible that you have installed an application that could be the issue?
i had this problem too for the first time last night. My notification light was flashing... pressing power button did not wake up.... I even long pressed power buttoin in the hope of getting the shutdown option, but nothing... i did a quick google search to see if there was a way of soft resetting, but couldnt find one, so pulled out the battery.
Its been fine since
No I only bought one of them but had to do an exchange on it because of it not waking up and the screen was getting dust under it. The exchange I got in the mail is still doing the wake up thing.
It's not due to pushing the button wrong I know that much haha. I'm a pretty skilled button presser
Well at least one person knows what I'm talking about. Let me know if it happens to you again
I have 2 nexus ones and one of then does have this issue. I have had it happen 3 to 5 times.
shep211 said:
I have 2 nexus ones and one of then does have this issue. I have had it happen 3 to 5 times.
Click to expand...
Click to collapse
Have you rooted either of them? I'm thinking it's some type of software glitch that might be fixed once new ROMs get cooked up but I've been holding off on rooting to preserve my warranty because of this issue.
Never had that problem.
Just so the forum doesn't just fill up with complaints.
mcarey66 said:
Have you rooted either of them? I'm thinking it's some type of software glitch that might be fixed once new ROMs get cooked up but I've been holding off on rooting to preserve my warranty because of this issue.
Click to expand...
Click to collapse
The one with the issues is rooted. I am using stock rom because I am sending it back soon.
mcarey66 said:
Okay I've been having this issue since I got my Nexus a couple of weeks ago. Several times a day I'll go to take it out of my pocket or pick it up off a table and when I go to hit the unlock button at the top nothing happens, the screen never wakes up. The trackball will still be lighting up as always but nothing on the screen. I have to pull the battery in order to get it to reboot so I can use it.
Due to this issue and getting dust under my screen I called HTC for a replacement. I got my replacement yesterday and got it all set up again. Within the first 2 hours I picked it up off my table and it wouldn't wake up. And this has probably 4 times since I got the phone yesterday.
Is ANYONE have this issue? I think it's a little weird it happened on my original device and now on my replacement.
Click to expand...
Click to collapse
iv been having this prob with the mt3g, tmobile is sending me a new phone im thinking its the htc keyboard apk or the nexus news widget apk, i have never had this problem till i put these two apps on my mt3g
Oh man! I thought I was the only one with this issue! It sometimes a couple of times a day and it's extremely inconvenient! I thought maybe my phone had gotten too hot and it froze or something but I could never figure out why it really happened. Mine is also rooted so maybe that's the issue? I hope someone finds the cause of this problem and even better, a solution, soon. It's pretty annoying, and one of the very few things that I don't like about my new partner.
I must be a lucky sob,beacause my nexus has no problems at all, working vib, no dust under screen, all buttons work, no problems at all (knocks on wood)
I'm having one issue and it can be annoying. Sometimes my screen just doesn't respond and if it does it's miles off. like if I press in the middle, the menu pops up as if the calibration is off by an inch or so. The annoying part is when a call comes in and I can't slide to answer which makes me miss a proper button.
My N1 is not rooted and a reboot normally sorts it out.
Edit: I forgot to mention that this almost always happens after I plug the charger like it is now arrrrgghhhhhhh.
I'm not having any issue with power on button and my N1 is not rooted (yet).
I did a DIY digitizer replacement a month or so ago, and its been working great up until a few days ago. Now, when I go to touch one of the soft buttons or type on the keyboard, the phone "flips out" and starts registering inputs in all random spots, sometimes getting stuck on that spot. I am totally stumped.
I double checked and all the ribbon cables are seated and such, and tried flashing over to Modaco rom from Cyanogen (thinking it might be software)... no luck. Can't even replicate it consistently, it seems to have a mind of its own.
Any thoughts as to what is going on?
Well I know that it has been an issue for some people and the general idea is that if you push the power button and put the screen to sleep and then wake it back up 20 seconds or so later it will work again. I have to say to also wipe your screen clean as well, build up on the screen can cause wonky behavior as well. Good luck.
Mike
this sounds exactly like the glitch that all nexus ones have, stock ROM. just lock then unlock the screen and it fixes itself.
the word is that it will be fixed with the 2.2 update. fingers crossed.
I thought it was that issue I read as well, but the power button glitch-fix everyone speaks of doesn't work.
I actually used my pry-tools to unseat the digitizer from the rest of the phone and kinda let it dangle, and 90% of the issues disappeared.
I am wondering if it might be the digitizer pressing up against the metal backing thats causing it to ground out and cause these issues, since the original phone was held in by a foam-type adhesive which I don't have on it now.
that's very possible. the power button resets my glitch 100% of the time. so sounds like something else is going on with yours.
RogerPodacter said:
this sounds exactly like the glitch that all nexus ones have, stock ROM. just lock then unlock the screen and it fixes itself.
Click to expand...
Click to collapse
I don't think its the famous touchscreen issue that we've heard because it was reported to register a click few centimeters below the touch point. Here in this case, the guy says that it randomly registers clicks at different spots.
AlexTheSquid said:
Now, when I go to touch one of the soft buttons or type on the keyboard, the phone "flips out" and starts registering inputs in all random spots, sometimes getting stuck on that spot.
Click to expand...
Click to collapse
I hope that reboot fixes this problem....
I've given up on the task for now, went back to my iPhone 2G till I can figure this out... its definitely not software though... and the digitizer still registers accurately when I don't have it seated into the phone...
No issues here on cyanogen 5. 0. 6 I love this Rom and have 0, yes I said it zero issues..... running solid for almost a month.... sorry ya have them issues I hope ya get em figured out...
As others says, just a quick lock & unlock fixes this. No need to wait 20 secs, I do it right away. Power, power, slide to unlock and I'm back in business.
For me I'd say it happens maybe a couple times a week? What about other people?
On stock it happened like once a week.... for me
none on custom so far after 3 weeks
yeah a couple times a week is it for me too. I wonder if view identified the issue and fixed it in the update. I'm sure some Google employees experience the bug.
So I've had my Nexus One since release at the beginning of 2010, and I'm finally coming out to ask: does anyone else have occasional trouble with their touchscreen detecting touches at completely the wrong places? At random points while using the Browser (maybe once or twice a week) I'll be trying to scroll and I'll get a quick zoom instead. Also, if I touch about 1 inch above the Back/Menu/Home/Search keys, they will be recognized as those keys instead of touching the screen! This bug happens outside of Browser too (though it always seems to start there) and has been consistent across CM6, MM's Gingerbread Builds, and several other ROMs. It always goes away with a reboot, but I just wanted to see if anyone else has had similar problems
I'd bet 99% of Nexus owners have this problem. You don't have to reboot, just turn your screen off and on again to reset it.
It's a hardware problem, the touchscreen panel isn't very good in the Nexus One..
But, It's fine in the newer phones like G2 and Nexus S
yup I have the same issue not a major issue I think battery draining & memory has been my main issue at the moment.
http://forum.xda-developers.com/showthread.php?t=878477
Since getting mine back from repair the problem occurs less often but is still there.
QuacoreZX said:
So I've had my Nexus One since release at the beginning of 2010, and I'm finally coming out to ask: does anyone else have occasional trouble with their touchscreen detecting touches at completely the wrong places? At random points while using the Browser (maybe once or twice a week) I'll be trying to scroll and I'll get a quick zoom instead. Also, if I touch about 1 inch above the Back/Menu/Home/Search keys, they will be recognized as those keys instead of touching the screen! This bug happens outside of Browser too (though it always seems to start there) and has been consistent across CM6, MM's Gingerbread Builds, and several other ROMs. It always goes away with a reboot, but I just wanted to see if anyone else has had similar problems
Click to expand...
Click to collapse
Same to you, I have this problem either.
I have swapped my n1 3 times and finally got one without this problem. I mean completely gone, not occur even once. So I suggest you swap it.
Same here. Yesterday, the half upper screen doesn't recoginze any input
helloworld1 said:
I have swapped my n1 3 times and finally got one without this problem. I mean completely gone, not occur even once. So I suggest you swap it.
Click to expand...
Click to collapse
Same here. My first one had the issue a couple times a day, the next phone was particularly bad with my screen screwing up every few minutes. This current phone hasn't had the issue in the month I've owned it.
Part numbers and the touchscreen panel part numbers are the exact same in the last two.phones.
This bug is a year old.
Amazingly I've never had that issue so I don't think its universal though my screen sometimes fails to respond at all but that'll go away after a minute or so.
RogerPodacter said:
This bug is a year old.
Click to expand...
Click to collapse
It's not a bug, it's a hardware defect. There is no way to prevent this in the software.
I only seem to get it when on charge, and there is a thread about the same thing in the NS forum, so it's not just us.
GldRush98 said:
It's not a bug, it's a hardware defect. There is no way to prevent this in the software.
Click to expand...
Click to collapse
Granted. However I can envisage a piece of software that cycles the screen off/on momentarily every few minutes that may in practical terms fix it.
My first N1 was only slightly effected by the screen fault, even after going back to HTC for a new power button. When the power button failed a second time I elected to go for a refurb on the second warranty return. Unfortunately the refurb is quite badly effected by the screen alignment fault.
Most annoying thing is when the alignment goes out, I have no choice but to use the power button to cycle it off. I am trying at all cost to avoid using the power button on my N1 to defer its inevitable next failure.
There's a fix for it
I can confirm that replacing Radio to "Korean Radio" solves this problem!
Verified in 4-5 different devices.
You can find the radio here:
http://forum.xda-developers.com/showthread.php?t=816917
Tomer
tomerbn said:
I can confirm that replacing Radio to "Korean Radio" solves this problem!
Verified in 4-5 different devices.
You can find the radio here:
http://forum.xda-developers.com/showthread.php?t=816917
Tomer
Click to expand...
Click to collapse
That's not entirely true... I'm on that radio and I have this issue from time to time.
As above, radio isn't a fix, can't think why it would be.
logger said:
Granted. However I can envisage a piece of software that cycles the screen off/on momentarily every few minutes that may in practical terms fix it.
My first N1 was only slightly effected by the screen fault, even after going back to HTC for a new power button. When the power button failed a second time I elected to go for a refurb on the second warranty return. Unfortunately the refurb is quite badly effected by the screen alignment fault.
Most annoying thing is when the alignment goes out, I have no choice but to use the power button to cycle it off. I am trying at all cost to avoid using the power button on my N1 to defer its inevitable next failure.
Click to expand...
Click to collapse
i avoid the power button too when i need to cycle the screen. i use cyanogen ROM which has the Zzz button in the drop down shade, which blacks out the screen. then just hit trackball to wake it back up. power button avoided!
RogerPodacter said:
i avoid the power button too when i need to cycle the screen. i use cyanogen ROM which has the Zzz button in the drop down shade, which blacks out the screen. then just hit trackball to wake it back up. power button avoided!
Click to expand...
Click to collapse
There is an app in the market for a buck, it's called screen off. It comes with a widget or app and one of the choices is an invisible widget so if you don't want to see it you don't, (just remember where you put it)...........
I use it for shutting my screen down all the time for saving battery life.
vinnyjr said:
There is an app in the market for a buck, it's called screen off. It comes with a widget or app and one of the choices is an invisible widget so if you don't want to see it you don't, (just remember where you put it)...........
I use it for shutting my screen down all the time for saving battery life.
Click to expand...
Click to collapse
I'm using the Lock widget to power down...it's free on the market! There's a transparent version in the Android theme section.
I got up this morning, grabbed my tablet, switched it on and found that no matter what, it wouldn't respond to touch input.
Hoping I could sort of "kick it" by using a keyboard I plugged one in and while that worked fine, it didn't unstick the digitizer.
Had to reboot.
Anyone else seen this?
I've had this happen once or twice, and as you mentioned the only way to get it to respond was by a reboot.
oooooo.... never happened to me for the full 6 day since i have this tab i suggest you turn then for replacement....
just remembered something are you guys by any chance use screen filter? that causes touch problems in some spots....
I'm using it on my phone but but not the iconia
its has happen twice in the last two days. Usually when the tab is left for a while hours. You're right the only way to unlock is to reboot.
thor2002ro said:
just remembered something are you guys by any chance use screen filter? that causes touch problems in some spots....
Click to expand...
Click to collapse
Na, I'm not using a screen filter. It happened twice in the first couple of days of owning it and hasn't happened for the last couple of weeks. I've had the same thing happen on the Desire HD a couple of times as well. It doesn't happen very often so I'm not overly concerned.
Jup, sometimes the screen doesn't respond. I found that if you rotate it (even with the lock on) and then turn on the device the screen wants to rotate and will then be unresponsive. Reboot and all is fine. Seems like a software bug to me.
Just in case you haven't done so, remove the sticker on the right border. It has a metallic back and interferes with the screen. I had that happen on a display model at BB twice withing 10 minutes. Once I removed it, no more problems. And I haven't had any problems with my purchased one.
A friend of mine bought one online and complained about the same thing. I told him to remove the sticker and the issue went away.
the sticker on mine was removed in the first five minutes. haven't had the problem again yet. hope it was a fluke
My rooted 32GB has just started doing this (2nd time this has occurred now). When I try to unlock, it just makes a click sound and relocks and blacks the screen. The first time resolved itself. Not sure if a reboot will help (probably so), but wondering if anyone has seen this or has any suggestions.
doncaruana said:
My rooted 32GB has just started doing this (2nd time this has occurred now). When I try to unlock, it just makes a click sound and relocks and blacks the screen. The first time resolved itself. Not sure if a reboot will help (probably so), but wondering if anyone has seen this or has any suggestions.
Click to expand...
Click to collapse
Is there any magnet near the N7? (if you have case, maybe the it is not working to well, most of the case is not prepared for daily use )
Ábel
Does the screen turn on and everything looks fine, but there is no touch response at all? Do the hard buttons prompt the menu's like power down and volume control but there is absolutely no touch input? I am asking these questions because if it is doing this you are having the same issue as me, I had been working on this issue for a solid month with absolutely no luck and the issue kept getting more frequent.I have re-flashed stock Google images both 4.1 and 4.2 with absolutely no luck. After the clean installs I did not root it I left the it completely stock and the issue is still there, also I thought it may have been my Poetic magnet case, well i took it out of the case and it still does it. I even removed my $20.00 dollar Steinheil Ultra Crystal Screen Protector thinking that may have something to do with it but that's not the issue. After every reboot it will work fine, so I was completely frustrated and could not find that many people on line with this issue. I finally had to send mine back to ASUS and they stated it was a screen assembly issue and they could replicate the problem, well I got it back last week and five minutes after booting it up the issue is still there so needless to say I have to RMA it again. What really bugs me is the Nexus 7 worked fine for two months not one problem then, I left it in a cabinet for 2 days without touching it and that's when the issue started and it has just gotten worse.
I apologize for the long story if this is not your issue but I just wanted to save you a lot of hassle if it is.
My issue isn't as complicated, fortunately for me. The screen is black (even though cover, with magnet, is open). I hit the power button once to get the screen to light up and slide the unlock. It looks normal but only flashes for an instant, then makes the click and the screen goes black again.
It self resolved again, so I actually am suspecting that it could be that when the case is folder over, the magnet may possibly be causing this. So thanks for that suggestion. Next time it happens I'll be looking specifically for that to see if I can narrow it down.