Database Develop

Screen unresponsive

Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.

mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2

This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium

It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium

Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium

I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium

mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result

@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium

Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?

mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result

xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2

Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium

Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?

I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!

Me too! on ICS
btw, i'm already on ics team nyx

change
flash CF KERNEL and put ICS CM9

middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.

psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium

same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?

I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk

[Q] Does everyone face screen flickering 12.1.A.1.201

Hey guys just looking for a definitive answer here. As 4.1.2 has no screen flickering bug, and on 4.3 it comes up automatically... I can assume its a software glitch rather then hardware .. then why isnt everyone having that issue? and why cant sony fix it.
I just updated to 12.1.A.1.201 and although the flicker has reduce, its still there in greys/blacks. Going back to 4.1.2 again.

magicali said:
Hey guys just looking for a definitive answer here. As 4.1.2 has no screen flickering bug, and on 4.3 it comes up automatically... I can assume its a software glitch rather then hardware .. then why isnt everyone having that issue? and why cant sony fix it.
I just updated to 12.1.A.1.201 and although the flicker has reduce, its still there in greys/blacks. Going back to 4.1.2 again.
Click to expand...
Click to collapse
cause sony sucks!! we said that.. they have your money they dont care any more i think a 20% at least have this flickering..
edit: check my thread and check the pictures http://forum.xda-developers.com/showthread.php?p=51553670

I have flickering bug on 4.1.2 with backlight turned off and auto brightness on
Sent from my C5303 using Tapatalk

I don't have any screen flickering things. Everything's normal with .266

hmm sound good to leave something here while watch what others feel about the new firmware before upgrading. Give some review guys

Just updated (only 9MB?!?!?). I'm on global generic firmware and still get the flickering screen with greys and blacks.
I don't think its as prominent as it was, and I definitely didn't get it with 4.1.2 software.
My screen is set to auto adjust its brightness and I think it's more noticeable when changing now.
That aside, its less laggy now!

The flicker issue was resolved by disabling adaptive brightness for me and some others but not for everyone.

Simple step...
Select wallpaper from album using google+ ( using scroll wallpaper)
Done
Hit the home icon 2 or 3 times
Problem solved.... Works for me.....

ArunThazhathuveetil said:
Simple step...
Select wallpaper from album using google+ ( using scroll wallpaper)
Done
Hit the home icon 2 or 3 times
Problem solved.... Works for me.....
Click to expand...
Click to collapse
That seems like an unnatural fix :S .. you have faced the screen flicker issue on 4.3 or 4.1.2?

magicali said:
That seems like an unnatural fix :S .. you have faced the screen flicker issue on 4.3 or 4.1.2?
Click to expand...
Click to collapse
Ha ha I will not even try it

ParaSense. said:
Ha ha I will not even try it
Click to expand...
Click to collapse
Neither will I

Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!

mrhnet said:
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
Click to expand...
Click to collapse
Doesn't work for me Thanks for the tip though

mrhnet said:
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
Click to expand...
Click to collapse
i have tried everything except pimp my rom... but i dont think it will solve this problem cause i have this flickering even in recovery (cwm,twrp) if 4.3 kernel is installed

ParaSense. said:
i have tried everything except pimp my rom... but i dont think it will solve this problem cause i have this flickering even in recovery (cwm,twrp) if 4.3 kernel is installed
Click to expand...
Click to collapse
Yes.. it looks like a issue at kernel level/gpu driver. But those workarounds worked for some. Maybe it could be another issue..
If you are still in 4.3, just type this in a terminal:
cat /d/clk/mdp_vsync_clk/enable
If it returns 0, type:
su
echo 1 > /d/clk/mdp_vsync_clk/enable
It fixed for some, but not sure whether it's the same "flickering" issue. Just a tip..

I have read this thread and (more other) and always wondering what are you people talking about??
Only flickering which I have seen on my sp was when I had auto brightnes on. But this is how auto brightness should work.
On 4.1 wasnt any flickering because auto brightnes didnt work on 4.1
On 4.3 work a little better, but not so good as for example in CM 11.
But when u turn off auto brightness there isnt any "flickering".

mrhnet said:
Yes.. it looks like a issue at kernel level/gpu driver. But those workarounds worked for some. Maybe it could be another issue..
If you are still in 4.3, just type this in a terminal:
cat /d/clk/mdp_vsync_clk/enable
If it returns 0, type:
su
echo 1 > /d/clk/mdp_vsync_clk/enable
It fixed for some, but not sure whether it's the same "flickering" issue. Just a tip..
Click to expand...
Click to collapse
I really dont want to install again 4.3 to try this (maybe it will work) not now at least.. but i will try it some time... thanks

Why Display is for few second yellow in build 205?

Hello
I flashed stock rom build 205 C5303 Middle East and i have a big problem that some time color display is yellow for 3_4 second and back to normal.
I haven't problem hardware.
Please help me.[emoji24][emoji31]

I also have this problems
I've tried to use PCC but didnt work

Make a picture (if possible) to show us. I think I know what you mean but still for clarification

I have this problem too!
First with 205 Telekom HU and now with eXistenZ 4.0. When this happens the screen is not responding.

I suggest you bring it to Sony While your warranty lasts...
Try flashing the .254 JB 4.1 FW before flashing any Stock Based Custom ROMs

hi dadash
i have this problem with the .205 stock kernel
i donno why sony dont give us a full working kernel
Edit : and i wanna add this : when this happens , screen freezes on a something like a screen shot from 2-3 seconds ago :-/
and now a question from who have this problem , you had screen flickering with with .201 ? cause i had . but in .205 fixed !

mosi.sh said:
hi dadash
i have this problem with the .205 stock kernel
i donno why sony dont give us a full working kernel
Edit : and i wanna add this : when this happens , screen freezes on a something like a screen shot from 2-3 seconds ago :-/
and now a question from who have this problem , you had screen flickering with with .201 ? cause i had . but in .205 fixed !
Click to expand...
Click to collapse
Hi?
Jump screen in 205 is fixed but yellow screen and stuck in some time is big bug.

Do you guys that have this problem all have the same model? C5302/C5303/C5306
Sent from my C5303 using XDA Free mobile app

My phone is c5303
So have me this problem in custom roms use base 205 and stock.

Mine is C5303.

I am having this issue also on ExistenZ 4.0 and I had it on a stock deodexed 205 ROM.
Its like the screen just stops responding and fades away as if the contrast/color just fades away to a browner image of whatever is on the screen, then after a few seconds, it pops back to normal contrast/colors and the screen responds as normal. Happens quite frequently with chrome for me, i'm going to look at alternative browsers, but im sure its happened while using the XDA app also, while scrolling through a board.
Edit: also happened in youtube while watching a video.
Edit 2: Fully restored my phone to stock with PC Companion and it gave me stock 205, the same fading happens, has to be a bug specific to 205 firmwares.

donk165 said:
I am having this issue also on ExistenZ 4.0 and I had it on a stock deodexed 201 ROM.
Its like the screen just stops responding and fades away as if the contrast/color just fades away to a browner image of whatever is on the screen, then after a few seconds, it pops back to normal contrast/colors and the screen responds as normal. Happens quite frequently with chrome for me, i'm going to look at alternative browsers, but im sure its happened while using the XDA app also, while scrolling through a board.
Click to expand...
Click to collapse
i have this issue to...

Sony needs to fix this ASAP
Everyone please send a complaint to sony so they can fix it

Stock .205 + CWM/TWRP for LBL + root + Deodex + most of "Junk" and standard apps removed + Black dialer, phonebook,conversations etc. (Only Settings and SEMCSettings white) yellow display happends after heavy load of CPU/GPU (Benchmark,game) for 1-2sec and everything goes back to normal. Happens only when i turn off heavy load app.

I am having this issue on 205
Model - C5303

Lets hope this is fixed in the upcoming 207 firnware!
Sent from my C5303 using XDA Premium 4 mobile app

But i dont have this issue in .205 . Model c5302 .
But i have this issue on .201 while playing gangstar vegas

[HELP]Weird Touchscreen Problem

Help[emoji21] So my problem is when I use a single finger(eg. Right Thumb) the touch doesn't work on my phone[emoji22](Nothing so unusual....right? But wait for it). However when I hold down a finger(eg. Left Thumb) on the screen and then use another finger(eg. Right Thumb) the touch works absolutely fine(Note that even though I've 2 of fingers on the screen, its getting registered as a single touch....not two). Now that is weird[emoji44]...
Now back to the case where a single finger is on the screen... As I said, the touch doesn't work...right? But it does work.... to a certain extent(I don't know how to put this[emoji28]...but I'll try anyway). Certain highlightable options(those in settings app, notification panel, etc) gets highlighted upon touching by a single finger... But I'm not able to scroll, open app, or anything touch related except highlighting(with a single finger). 'Show Touches' under Developer Options doesn't show this touch.
I'm on Lineage OS and I'm pretty much sure this wasn't supposed to be a ROM feature(As I faced similar issues on Resurrection Remix). Also, sometimes when I reboot, the problem gets resolved until next reboot. I had recently replaced the digitizer(by myself). So I'm not sure whats causing it..... If only someone could help[emoji25]
Sent from my Cloud_Cube using XDA-Developers Legacy app

Have u tried Mokee ROM? It's pretty good! My issues same as yours got mostly fixed by switching to this ROM.

lamtrinhan1503 said:
Have u tried Mokee ROM? It's pretty good! My issues same as yours got mostly fixed by switching to this ROM.
Click to expand...
Click to collapse
thnx for the reply I really appreciate it... I will surely try Mokee ROM and hope that fixes it

Is the problem solved? Cause I have a same issue with my xperia. First I used Stryflex Marshmallow then changed to Stryflex Lollipop and now I am using CM 14.1 But the problem still there :crying:

Brah ! Just flash doom lord kernel using flash tool and fastboot
Then boot sequence is
1when your phone turned on and you can see sony logo then continuously press vol down button after that you have to wipe/factory reset your phone and then wipe cache partition then wioe dalvik cache in advanced tab then install/flash the zip(ROM) you want.