Ok so, since I am new to actually USING XDA. It wont let me post into that thread to ask this question, even though I have searched it up and down for answers. I do understand that the OP(randomblame) says that there is a black screen issue after unlocking the device. I don't have that issue. What I DO have is very odd and not mentioned. On specific apps, the screen will go blank to just a backlight if I click on something. For example, in the phone app I can dial the number and everything is fine, as soon as I hit the call button, screen goes blank backlight. Same thing happens when watching video on youtube app, or hitting the search button. I always have to lock it, then unlock it to get my screen back. This is especially a problem when someone is calling, no screen.
Very wordy yes, if you need me to clarify I'd be happy to. Thanks for any help
I read somewhere that this happens even on the cm10 version and no fix or direct cause has been found yet.
Sent from my Inspire 4G using xda premium
I had the same issues. Used beta 13 with no problems but tried the release version 5 and 7. Still had black screen. Tried 7.2 and so far it will do it but not as much.
Sent from my Inspire 4G using xda app-developers app
TheManInYourSoup said:
Ok so, since I am new to actually USING XDA. It wont let me post into that thread to ask this question, even though I have searched it up and down for answers. I do understand that the OP(randomblame) says that there is a black screen issue after unlocking the device. I don't have that issue. What I DO have is very odd and not mentioned. On specific apps, the screen will go blank to just a backlight if I click on something. For example, in the phone app I can dial the number and everything is fine, as soon as I hit the call button, screen goes blank backlight. Same thing happens when watching video on youtube app, or hitting the search button. I always have to lock it, then unlock it to get my screen back. This is especially a problem when someone is calling, no screen.
Very wordy yes, if you need me to clarify I'd be happy to. Thanks for any help
Click to expand...
Click to collapse
That actually sounds more like a separate known backlight bug, one where the screen goes off on system sounds. The devs know about it and are working on it. All JB Ace ROMs have it to some degree. A workaround to make it happen less is to turn off all system sounds in Settings -> Sounds.
After using jelly time 7.2 for half a day black screen bug came back. Now I am back to beta 13.
Sent from my Desire HD using xda app-developers app
The code fire and unofficial cm10 nightly roms have been fixed as far as black screen bug.
Sent from my Desire HD using xda app-developers app
Thanks for the responses everyone. I believe I might have found a work around for the black screen. It has something to do with the system theme. If you go download any theme and apply it, no more random black screen in any app! This solved the problem for me, I encourage anyone else to test my theory.
He just put out R8 too which fixed both screen issues and camera. Just FYI.
Sent from my Inspire 4G using xda premium
Gizmoe said:
He just put out R8 too which fixed both screen issues and camera. Just FYI.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Haven't had a chance to test R8 yet. Didn't know if all screen issues had been truly fixed.
Gizmoe said:
He just put out R8 too which fixed both screen issues and camera. Just FYI.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Yup I've been using R8 since last night and the first system sound going to blackscreen is gone and the backlight staying on sometimes after locking is also gone.
TheManInYourSoup said:
Haven't had a chance to test R8 yet. Didn't know if all screen issues had been truly fixed.
Click to expand...
Click to collapse
Paulb-nl found the solution to the backlight bugs and Jellytime R8 has been updated to include the fix
Related
Hello guys I was wondering if anybody else is having this problem, sometimes when I press the back key on my att nexus s it freezes for a couple of secs then it goes back to normal, it won't matter what I am doing it could be anything from visiting the marketplace to browsing the web its really annoying me a lot at this point.
If you know anyway how to fix this issue please let me know thanks.
I have the same problem, but it also happens with my menu and search keys. The individual backlight will dim and the phone freezes for 4-7 sec.
Sent from my Nexus S 4G using XDA App
Not having this issue.
Sent from my Nexus S 4G
Is the phone freezing or is just the back key randomly not responding to touch? If its the latter, then you need to do an exchange. Common problem.
I used to have this issue but it eventually went away. It happened after they replaced my screen.
I used to have this and assumed it was a hardware thing, changing roms sorted it.
I have no idea why this is the case and when someone else said as much I thought it couldn't be the case but I'd suggest you flash a different ROM and see how you get on.
I have this problem also. Mine will go dark and exit out of anything I'm doing as if I was pressing it. Gets old sometimes
Sent from my Nexus S 4G using XDA App
http://www.google.com/support/forum/p/Google+Mobile/thread?hl=en&tid=455215ff8747658b
I started getting this about two months into the life of my Nexus. In the process of exchanging mine now in the hours that I get an unaffected unit.
Sent from my LG-P509 using XDA App
My first one did this constantly so I exchanged it and so far so good with the new one.
Looks like a bad batch of ns4g's went out. Mine is doing this too. Not very ofter but enough that I notice it.
tdavis42 said:
Looks like a bad batch of ns4g's went out. Mine is doing this too. Not very ofter but enough that I notice it.
Click to expand...
Click to collapse
Actually it affects all Nexus S models. I think it is touch panel driver bug.
Sent from my LG-P509 using XDA App
I feel like it deserves its own thread in the General section as the other one mainly pertains to ICS development.
Anyways, my voice to text was working flawlessly at first but not anymore. Anyone else having the same problem?
And if you're still unsure about running it, here's a short vid on it and how it runs.
http://www.youtube.com/watch?v=IInyumYOtu0
anyone have problems receiving SMS after sending one?
jdmcl9 said:
anyone have problems receiving SMS after sending one?
Click to expand...
Click to collapse
I haven't. What does it do when you try to send another one?
i get a weird problem that went im in the messenger app, if im typing in landscape and then go back to portrait the screen has a weird black overlay and I cant really see anything... it wont go away unless i restart the app... other than that stuff is running fine
Edit: I think this is a known problem because its an "android 4" app... he mentioned they would be glitchy
mackster248 said:
I haven't. What does it do when you try to send another one?
Click to expand...
Click to collapse
Its kind of strange, people can receive my messages but I won't get theirs when they reply. I've tried wiping cache and reflashing but it was still a problem.
JHaste said:
i get a weird problem that went im in the messenger app, if im typing in landscape and then go back to portrait the screen has a weird black overlay and I cant really see anything... it wont go away unless i restart the app... other than that stuff is running fine
Edit: I think this is a known problem because its an "android 4" app... he mentioned they would be glitchy
Click to expand...
Click to collapse
Yeah hardware acceleration isn't really fully working yet since its just a hack at the moment. That's why apps that utilize it are still weird at the moment. But hopefully he is able to fix that in the near future.
Sent from my LG-P999 using xda premium
jdmcl9 said:
Its kind of strange, people can receive my messages but I won't get theirs when they reply. I've tried wiping cache and reflashing but it was still a problem.
Click to expand...
Click to collapse
That's really odd... Its working fine for me. Does it work fine on your GB ROM?
Sent from my LG-P999 using xda premium
The brightness only adjusts the capacitive buttons, not the screen.
Sent from my G2X
zoppp said:
The brightness only adjusts the capacitive buttons, not the screen.
Sent from my G2X
Click to expand...
Click to collapse
Really? Brightness works fine for me.
Sent from my LG-P999 using xda premium
Boot loop
I posted on General ICS thread before I saw this one, but I used G2x Scrubber and I have tried normal Factory Reset, and Than I flash CM9 and Gapps( for 4.0), but it gets stuck at the Lg screen and goes into bootloop... I can still get to recovery but I cant get CM9 to work any suggestions?
mackster248 said:
That's really odd... Its working fine for me. Does it work fine on your GB ROM?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yeah everything works perfectly on my GB rom and I receive my messages when I go back to my old rom which is pretty strange.
mackster248 said:
Really? Brightness works fine for me.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Never mind. Just needed a reboot.
Sent from my G2X
wifi wont turn on
JHaste said:
i get a weird problem that went im in the messenger app, if im typing in landscape and then go back to portrait the screen has a weird black overlay and I cant really see anything... it wont go away unless i restart the app... other than that stuff is running fine
Edit: I think this is a known problem because its an "android 4" app... he mentioned they would be glitchy
Click to expand...
Click to collapse
this should fix that http://kan.gd/1g6l
follow RC on G+
ayysir said:
wifi wont turn on
Click to expand...
Click to collapse
Try rebooting.
Sent from my LG-P999 using xda premium
The only real issue I have is when I tap the screen, sometimes it'll act as if I'm holding down on where I tapped. Camera works for me now, but attempting to take picture make it not respond, asking me to force close. Still, it's good been good enough to use all day for me.
Sent from my CM9 G2x
does gps work correctly??
Camera doesn't work, any suggestions? It will start up and take a picture but then freezes.
get the camera 360 app from the market. it works perfect for me.
GPS works. Not sure if it's more or less stable than Gingerbread though.
Sent from my LG-P999 using XDA App
Hey there xda people, just wanting to let you people know that the WidgetLocker (app) for me at least causes some multi touch problems with the one x.
The problem that it causes is whenever your holding one finger down on the screen to like say control a virtual analog for a game so you can move around and then tap anywhere on the screen to shoot or something. The first finger hold gets wiped out and causes movement to stop. All in all its causes a horrible experience while playing games.
I was having this issue forever until today when I wiped my phone clean and everything works fine with games and stuff until I installed WidgetLocker and I get the issue again. So this issue was fixed when I stopped using the app.
Not sure if a lot of people uses this app but I've been using it since I bought my first Android (sgs ii) and it's a great way to customize your lock screen with widgets and stuff. I'm definitely going to let the developer know about this bug when I have time, my guess as to why this happen is the way that it unlocks your phone that messes up the multitouch.
Sent from my HTC One X using xda premium
I just tried uninstalling Widget Locker on Nocturnal 111 and I am still getting this bug. I will try to reboot and see if that fixes it for me
Sent from my HTC One XL using Tapatalk 2
MyronJ906 said:
I just tried uninstalling Widget Locker on Nocturnal 111 and I am still getting this bug. I will try to reboot and see if that fixes it for me
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I didn't have to restart, just had to lock the phone then unlock it again with the stock lockscreen.
Sent from my HTC One X using xda premium
You are right. When I woke up this morning, it was fixed.
MiLocker causes the same issue... How sad.
Sent from my HTC One XL using Tapatalk 2
Glad to see your issue was fixed. The good thing though is that I'm in love with my phone again lol.
Although I was trying out cm9 alpha 3 earlier this week and I'm pretty sure I was getting the same issue without WidgetLocker. Maybe the locker with cm9 causes this issue as well?
I could be wrong with cm9 though as I may have downloaded the app but didn't use it so that could've cause the problem as well.
Sent from my HTC One X using xda premium
I ran into this issue a while ago... here is a thread I started about it: http://forum.xda-developers.com/showthread.php?t=1665603
I never did resolve the issue (aside from disabling Widget Locker), nor did I get around to contacting the developer...
However, it appears this does not affect all One Xs using WL as several other people tested and were able to use Widget Locker with out breaking multitouch on the One X.
I checked out this and mesaone's thread as I was having this issue too. Turns out I was able to fix it by disabling HTC gestures in the Display & Gestures settings menu. DoomGLES now runs without a hitch and I'm able to both move and fire/open doors at the same time. I haven't tested much beyond the DoomGLES test but if anything changes I'll report back.
EDIT: It appears the solution was short-lived; quitting fully out of the applications, turning off the screen, turning it back on and unlocking and then relaunching the app caused the issue to return. On the other hand, simply disabling widget locker for the duration of the game works fine (and unless you're turning your phone off and on a lot while playing games, probably not a big deal). No need to uninstall.
ONe X and Widgetlocker
I have had Widgetlocker for 2 years on my HTC desire. Now upgraded to One X and I have a problem with answering calls.
If the phone is locked and I get a call, I get the call answer option but then have to put in my unlock number. By this time the caller has hung up. Previously on my HTC desire I could answer by pulling the screen slider down even if the phone was locked.
Have I missed a setting??
Help would be good
Thanks
TA
The only option would be to not use widgetlocker if you don't want to have problems (that is if you do have problems). I want to confirm that this issue occurs in CM9 even without the widgetlocker app, not sure if others are getting this issue but I suppose I'll be CM9less till it is addressed and fixed.
Sent from my HTC One X using xda premium
tizzie said:
Glad to see your issue was fixed. The good thing though is that I'm in love with my phone again lol.
Although I was trying out cm9 alpha 3 earlier this week and I'm pretty sure I was getting the same issue without WidgetLocker. Maybe the locker with cm9 causes this issue as well?
I could be wrong with cm9 though as I may have downloaded the app but didn't use it so that could've cause the problem as well.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
CM9 and AOKP in general currently have a multitouch bug, whether its with WidgetLocker or not.
Anyone had dead spots on their HOS?
On two different occasions, the screen stops working directly above the Homebutton and a reboot solves the problem..
But since it happened 2 time now, is my digitizer damaged or something?
Similar problem
I seem to have a similar problem where I get random dead spots on the screen. The problem happens more frequently with me with AOSP ROMs. Also, turning the screen on and off usually fixes it for me. I may have a bad digitizer, I'm not sure though.
I've had the same issue couple of times a while back.
edit
can't remember, but it might've been while using cm10 (only had it on for a few days).
Try downloading dead pixel fix from market it is really good fixing dead pixel
Download run the app and leave or phone for at least 6 hour with app running at maximum brightness
Sent from my HTC One X using xda app-developers app
Sorry, I didn't mean dead pixels, I meant the touch gets dead..something with the digitizer...
Dude I had a post about this before like i have to turn my screen off a lot cause it won't register my space bars during a text or the letter t and its really annoying but turning the screen off and on fixes it
Sent from my HTC VLE_U using xda app-developers app
I been having a similar issue usually made the center of the screen around the t y u Button's on the keyboard.
Started roughly after running cm10 might be a coincidence though
Sent from my HTC One S using xda app-developers app
Try wiping off the screen and turning the phone off and on.
The first might help if it's a humidity issue, the 2nd might help if it's a grounding or static issue.
I don't have these issues but is it related to this? http://forum.xda-developers.com/showthread.php?t=1679649
Touch Button Issue HTC One S
It's pretty much the opposite of that issue to the point where il be trying to get in the menu and my touch on the menu key doesn't do anything till I turn my screen off and on cause the bottom part of the screen is unresponsive... And I'm on stock no root
Sent from my HTC VLE_U using xda app-developers app
Yeah I had like 2 of em. Got them handled in service.
Hunt3r.j2 said:
Try wiping off the screen and turning the phone off and on.
The first might help if it's a humidity issue, the 2nd might help if it's a grounding or static issue.
Click to expand...
Click to collapse
+1
This!! I always have to do this once in awhile.
This only happens in aosp roms (dont know yed on aokp). It used to happen to me sometimes on cm10 but now I´ve been for a while on sense roms and didn´t happen anytime.
i agree with the above, ive only had this issue on cm10
I run into the same problem sometimes. It's most noticeable when using the keyboard but I've had it happen on another part of the screen. Like others have said turning off the screen then turning it back on always worked to fix it.
I was having this issue in CM9... Once I reverted back to Trickdroid 7.1, this issue no longer happens. So it sounds to me like it's related to the driver in CM9... I suspect that if I switch to CM10, the issue will still be there.
I haven't seen anything else posted, but I wanted to see is anyone is having the same issue as I am.
Basically, I'm getting what I think are row's of pixels flickering in the area of the screen that are gray.
Here is a quick vid trying to capture it. I can't post videos because I have less than 10 post, you are going to have to trust me for now...
I've also used the dead pixel finder app...everything looks good until I change over to a gray screen, if I stare at it, I can see the flicker...
I first noticed it when I flash Franco r10 (which is what I was on in the video). When I flash back to stock kernel or Bricked, it's much better. But now that I know it is there, I can still see it.
Anyone else having this issue? is there a fix or should I just send it back?
If it matters... LG-D820 White, 32gb
I'm guessing I'm alone with this issue and that it is a hardware problem. :thumbdown:
Sent from my Nexus 5 using xda app-developers app
motoguy said:
I'm guessing I'm alone with this issue and that it is a hardware problem. :thumbdown:
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I haven't noticed anything on mine, but I haven't flashed anything yet. Did you notice the flicker before you flashed the first time?
No I didn't notice anything until I flashed r10. But now that I'm looking for it, I can see it on stock and bricked ever so slightly.
I could live with it on the stock colors, but if this is hardware, I worry that it is going to get worse and not better over time.
Sent from my Nexus 5 using xda app-developers app
I have the same issue and saw it as soon as I flashed franco kernel. Noticed that if you set brightness to 100% it will slowly stabilize but will still come back when lowing brightness. I called for an RMA, but cannot reproduce it as obviously on stock, so i'm also lost as to what it could be.
What did you end up doing?
On mine, I could see it on Stock colors, just not as bad... I returned mine on rma....
I recommend getting the app called display tester.
I don't have enough post for a proper link.
https:// play.google.com /store/apps/details?id=com.gombosdev. displaytester
Look for a bad pixel and go under the banding section for reason for rma.
My new phone didn't have any of the flicker /banding that my old phone did.
Good luck..
Sent from my Nexus 5 using xda app-developers app
My screen flickers too but ppl told me its normal
edit. found link http://forum.xda-developers.com/showthread.php?t=2532955
Mine had nothing to do with animation.
Looking at my static wallpaper my screen would flicker....
https:// w w w.dropbox.com/s/az50k6x0jl4iab6/VID_20131113_143543.m p 4
Sent from my Nexus 5 using xda app-developers app
Sorry to bring back an old thread but I just noticed this not too long ago and didn't want to open a new thread. I noticed it while I was on stock first and thought flashing something might fix it. I've had mine since the beginning of November. Is the best option just to RMA it?
Sent from my Nexus 5 using Tapatalk
can you use a SlimPort cable or chromecast to mirror the screen to a TV and see if the flicker still happens?
So you'll know if the problem is in GPU or screen?!