[Q] Flashing/blinky screen in black but only on "application level" of display
Hey folks,
So what I'm seeing is the application area/layer of the screen blacking-out in a blinky way, and this seems to happen when there's screen updates like from the application or when I'm scrolling with my finger. The weird thing is this only seems to affect the "application level" layer -- the Status bar and other things like CPU usage (and overlay apps like SwipePad) are unaffected and don't black-flash.
I'm running PAC-MAN ROM (Android 4.4.4) but have experienced this on other ROMS so I think this is either a Note i717 thing and/or something that I'm doing to create this issue. It actually happened with less intensity with other roms of previous Android versions. (probably back to 4.4.2)
What I done wrong? I'm getting a hurt real bad. (a Russell Peters reference, for those who haven't heard his older material)
mentalfloss said:
Hey folks,
So what I'm seeing is the application area/layer of the screen blacking-out in a blinky way, and this seems to happen when there's screen updates like from the application or when I'm scrolling with my finger. The weird thing is this only seems to affect the "application level" layer -- the Status bar and other things like CPU usage (and overlay apps like SwipePad) are unaffected and don't black-flash.
I'm running PAC-MAN ROM (Android 4.4.4) but have experienced this on other ROMS so I think this is either a Note i717 thing and/or something that I'm doing to create this issue. It actually happened with less intensity with other roms of previous Android versions. (probably back to 4.4.2)
What I done wrong? I'm getting a hurt real bad. (a Russell Peters reference, for those who haven't heard his older material)
Click to expand...
Click to collapse
If you would consider this a screen flicker, you may want to try disabling HW Overlay in the developer options.
Another option may be to read up on POLLUTIONS "Patch". There is a thread for it, but I cannot say as to what issues it will fix. Apparently it is a miracle cure in tye Beanstalk thread.
Thats why I say....read on it first.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
If you would consider this a screen flicker, you may want to try disabling HW Overlay in the developer options.
Another option may be to read up on POLLUTIONS "Patch". There is a thread for it, but I cannot say as to what issues it will fix. Apparently it is a miracle cure in tye Beanstalk thread.
Thats why I say....read on it first.
Click to expand...
Click to collapse
Yeah those are some good ideas, but here's some more info:
I don't have the HW Overlay option enabled.
The "flickering" is not the entire screen, and it's more like a "black flicker", and ONLY on the "application layer"
I found the patch you mentioned in this thread and I'll see if it addresses it when I get a chance to work on the device.
Oddly, I just booted the phone with OTG HDMI connected to a monitor and the flicker is gone! :/ Not really a solution but an interesting oddity.
Related
Sometimes my touchscreen will be terrible, their will be no response at all.. and it will grab, but it will be in the wrong places, ive only found this problem whenever i rooted and reflashed with das bamf so far, and it blows because its literally the only problem i have now after being so happy with this root/rom deal so far.. i never flashed a kernal, so would that have something to do with it, or are kernals necessary to do? i have no idea what one even is to begin with so if that will improve the keyboard and or permit it from failing that would be worth looking into.. or is their a way to increase sensitivity on the phone somehow?
Thanks!
It's not going to be a kernel issue. Kernels do effect how some things work, but the Bamf team pair their roms with a kernel they find most suitable with their work. Kernels are mostly for setting CPU speed and Voltages.
I don't think your issue is a rom/kernel related issue. Does this problem persist when you turn off the screen and turn it back on? Sometimes if you get sweat or moisture on the screen, it tends to freak out. Another thing you can try doing is just reflashing your rom. I remember putting the leaked OTA Gingerbread on my ex's Droid X and after 2 weeks, the screen started selected itself dead center of the screen. Reflashed the rom, and it hasn't done it since.
If all of these things fail, than you have a hardware issue I presume. I wish you luck
Does your problem occur consistently all the time, or only in certain situations?
I.e: When the screen has been off? When exiting certain apps, etc?
If it only happens in certain situations, it may be a clocking issue that is causing the "lag" response.
The only way ive found to fix it so far has been to wipe the screen down every time before use, but i find that odd because with the factory rom back when i never had to.. so i guess its just more suspectable to elememts interfearing with the actual screen.. i havent changed screen protectors or anything.. The craziest thing to me so far..
Which version of DasBAMF are you running? I have a similar problem with their Sense 3.0 roms. The buttons on the MLB at bat widget and the refresh button for the Pulse news widget seem to work only intermittently.
Dr.Oid said:
Which version of DasBAMF are you running? I have a similar problem with their Sense 3.0 roms. The buttons on the MLB at bat widget and the refresh button for the Pulse news widget seem to work only intermittently.
Click to expand...
Click to collapse
2.01.605.0_Bamf_GingerREMIX_v2.1
Dr.Oid said:
Which version of DasBAMF are you running? I have a similar problem with their Sense 3.0 roms. The buttons on the MLB at bat widget and the refresh button for the Pulse news widget seem to work only intermittently.
Click to expand...
Click to collapse
The problems with your widgets may be related to the resizing issues with the 3.0 rom and where on the screen you have to tap for it to recognize the tap. I think many have been fixed, but there may be still some odd ones here and there.
Dnakaman said:
The problems with your widgets may be related to the resizing issues with the 3.0 rom and where on the screen you have to tap for it to recognize the tap. I think many have been fixed, but there may be still some odd ones here and there.
Click to expand...
Click to collapse
The Widget? i dont understand how that can effect the touch screen.. i had the news one on my home screen.. or am i not reading this correctly?
Willis_G said:
The Widget? i dont understand how that can effect the touch screen.. i had the news one on my home screen.. or am i not reading this correctly?
Click to expand...
Click to collapse
I was pointing out an issue with widgets on Das BAMF 3.0 as a specific example of an issue you might have. This point is not relevant since you are running 2.1.
Dnakaman said:
The problems with your widgets may be related to the resizing issues with the 3.0 rom and where on the screen you have to tap for it to recognize the tap. I think many have been fixed, but there may be still some odd ones here and there.
Click to expand...
Click to collapse
On RC5, the 2 widgets I mentioned are still wonky. I'm sticking with 2.1 remix for now.
Do you have any kind of screen protector? I get that from time to time when my screen is dirty and as you said wiping it down has always fixed it.
ScoobarSTI said:
Do you have any kind of screen protector? I get that from time to time when my screen is dirty and as you said wiping it down has always fixed it.
Click to expand...
Click to collapse
Yeah, do screen protectors fade over time? as stupid as that sounds ive had this one on my phone for six months.. is it starting to break down or something?
also my next theory is temperature.. when my phone is exposed to hot areas it doesnt react.. i noticed that tonight
Has anyone noticed a change in how the touchscreen behaves after installing ICS?
It seems to me that it is biased a little more towards interpreting a touch as swipe or scroll rather than select. For example clicking links in a webpage or tapping icons on the homescreen seem to require a much more deliberate effort to select/open. It's not awful, but I would like to be able to bias it back a little more to selecting rather than swiping.
Is there a setting for this anywhere or an app available that allows adjustment?
I would to know too.. I hate this..
But it's not just from latest ICS 4.0.3 International, the Beta version also suffer same thing.
Is HC not like this? (I upgraded to 4.0.3 Beta as soon as after bought Mediapad )
Yes, I noticed it also. When you turn on Settings - Developer options - Pointer location, it clearly shows how your clicks/dots becomes swipes/lines.
yes, you're right.. it sometime (most time ) cause texting experience not so fluid (letter not appear as it's detected as swipe not click).
got the same thing.. i've changed the launcher, so with the Apex launcher it's not that bad in the homescreens.. when i enabled the option to show "pointer location" i can see the "tap" as a line, or a "swipe" line :\
tried the same on my Galaxy S, and all the "taps" are only a small point.. it's much better than on the MediaPad.. i hope it's just a software issue and it can be solved..
maybe, we could try something like "screen booster" or "touchscreen booster" from the Market (Play)
Erratic screen while charging
The other thing I've noticed after ICS international is that the touchscreen is now erratic while charging and in a case. I believe this is a common problem with capacitive touchscreens, but hadn't noticed it until after flashing ICS. It is not an issue if I remove the pad from the case and hold it in my hand.
Anyone else seen this?
This sensitive touchscreen isn't Angry Birds friendly. Constantly shakes a little bit.
soooo.....is there any solutions?
noaustin said:
soooo.....is there any solutions?
Click to expand...
Click to collapse
Not unless huaweis coders tweak it or releases the source code.
I've only noticed this since about a week.
Its most prominent when I'm in text based apps - Pulse/Verge/Kindle - with a lot of white background.
To describe it - its like a 3mm thick 'glitch', appears for hardly a few milliseconds - just enough to be noticeable.
Its always along the length of the device, and does not matter what orientation I'm holding it in.
I felt it happened more often with auto-brightness but that feeling may just be a dud.
The recurrence is quite random, but I can easily see it if I stare at the screen for even a minute.
Finally I've never noticed it in games or on home screens - not sure if thats just because I miss it in those or otherwise..
I noticed this yesterday for the first time when reading some text. It was very distracting, hoping it was a fluke deal.
Seconding this. I don't have auto-brightness, but I notice it. Definitely happens when reading text with a white background - so get it pretty often in RSS readers, rarely in gmail, and never in games / movies.
Thanks for the replies..
I also noticed this never happens in gmail or currents. Looks like Google-supplied apps run fine...
This leads me to believe that these other apps are doing something wrong, maybe overflowing buffers due to the massive resolution as someone else projected in another thread...
Have you guys played with either the "Disable HW Overlays" or "Force GPU rendering" settings to see if they impact this issue one way or another?
Ravynmagi said:
Have you guys played with either the "Disable HW Overlays" or "Force GPU rendering" settings to see if they impact this issue one way or another?
Click to expand...
Click to collapse
I second this idea.. please try and report the results.
Since my last soft-reboot, I've yet to see ant tearing. However I'll try those options if I see it happening again. Thanks for the suggestions. Maybe some of the others seeing this can try those tweaks?
Happens to me no matter what app I'm running and has been happening since I got my nexus. Even just happened in the app drawer. I will check the force gpu settings and get back to you.
Sent from my Nexus 10 using xda app-developers app
phoenix79 said:
Happens to me no matter what app I'm running and has been happening since I got my nexus. Even just happened in the app drawer. I will check the force gpu settings and get back to you.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Force GPU rendering changed nothing for me. Still got the screen tearing. I'm going to try the Disable HW overlays for a while now.
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
For the past week or so my phone has had flickering multicolored lines flash across the homescreen(s)/lockscreen when I turn the display back on. Sometimes it will also happen if I'm sitting on the homescreen with the display already on.
Here is my Rom history as the problem began:
Was on supernexus (Android 4.2.2 I believe) - issue was not present
Flashed Unofficial Slim build 6 (wiped cache/dalvik/factory reset before install)- started having the issue
Flashed Unofficial Slim build 6.2 (wiped cache/dalvik)- issue still present
Flashed AOCP 5.7 yesterday (wiped cache/dalvik/factory reset and formatted internal SD)- thought issue was gone, but it started happening again today.
I tried taking screenshots but the issue disappears as soon as I press the volume+power button to take the screenshot. This only seems to happen when I'm on the homescreen/lockscreen, I dont think it has happened while in any other apps.
I'm wondering if this might be an issue with the specific version of the Nova launcher, as I believe that is the common denominator between these Roms (isn't AOCPs launcher based on CM's nova?). I just installed go launcher and the problem seems to be gone (for now).
Has anyone else seen something like this? I apologize if this has been discussed somewhere, I spent several hours searching Google and XDA before posting. I can post a picture later when I have access to another camera phone.
Same issue here
I have the same issue at the lock screen. Prevalent on all JB roms I have tried, carbon, revolt & slim bean.
I'm currently using Carbon nightly. I have not seen a fix for this yet. I have heard it might be an issue with the processor waking up from sleep.
After installing Go Launcher Ex opening it a couple times and then going back to using the Aspire launcher that came with AOCP, I haven't had this issue again all afternoon. Didn't have it at all yesterday though, so it might come back.
I played around with all the brightness settings but it didn't seem to do anything. Do you happen to have any pictures of the effect you are getting? I'll try and post a picture of mine tonight if it happens again. Thanks!
About 3 hours ago, I changed some GPU & lock screen settings and the issue has not reappeared.
I will post back either later tonight or tomorrow morning with some info.
I haven't taken any photos of the problem yet. By the way, do you usually experience the issue on lock screen coming from a screen off state?
ditto on this. I have Cyanogenmod 10.1 installed and I get these lines intermittently.
Try turning off CRT animations and disable hw overlays.
Sent from my SAMSUNG-SGH-I717 using xda premium
disabling hardware overlays always fixes it for me
same issue
Have the same issue going on had freezing and resolved that now I'm stuck on these lines multiple diff ROMs I am running cm10 I see people saying he overlays can someone provide a little more info on what that is and where to find it? Attaching screen shots of these multi color lines we speak of
Nvm can do it with the browser will edit this later and add them with a pc
nimixes said:
I am running cm10 I see people saying he overlays can someone provide a little more info on what that is and where to find it?
Click to expand...
Click to collapse
Go to settings, developer options scroll half way down and you will find it. You will have to disable it every time you reboot or you can use two paid apps from the market. These apps are tasker and secure setting they are both worth every cent.
Sent from my SAMSUNG-SGH-I717 using xda premium
Do you have any backlight handling apps? I used lux all the time and it stopped after I disabled it.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Just enabled "Disabled HW overlay" and "Force GPU rendering". Like some of the users suggested, I found about the possible solution from this video:
http://www.youtube.com/watch?v=yhhPPke_Nbw
(go to 1:40)
I usually get the flickering with the lock screen (I use WidgetLocker Lockscreen). I was having some flickering this morning and checking both of those options seemed to immediately cut out the flickering.
I ran across it(the flickering lines) on one of the 4.2.2 roms, can't remember exactly which one but what I ended up having to do was disable one of the tweak apps it came with and install Trickster Mod only. Worked for me, no more flickering or rebooting, not sure what the cause may have been but have had no other issues after that for I believe it was 2 weeks
Please elaborate
Demmonnixx said:
I ran across it(the flickering lines) on one of the 4.2.2 roms, can't remember exactly which one but what I ended up having to do was disable one of the tweak apps it came with and install Trickster Mod only. Worked for me, no more flickering or rebooting, not sure what the cause may have been but have had no other issues after that for I believe it was 2 weeks
Click to expand...
Click to collapse
By chance can you give some more details about this Trickster Mod like where to find it and what it is supposed to do?
A link to a thread would be great
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
nimixes said:
By chance can you give some more details about this Trickster Mod like where to find it and what it is supposed to do?
A link to a thread would be great
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301558&page=22
Scroll down to my post there. If you still need help, just let me know.
Trickster mod I believe is mainly for Rom's that have Kernels that can be OC'd or Under Clocked. Kind of the same as Android Tweaker or SetCPU but is a little smoother for me IMO.