Database Info

[Q] Samsung Galaxy SL i9003 screen unresponsive

the touchscreen of my samsung galaxy SL i9003 stops responding about 5 seconds after i unlock the screen.
I have done factory reset but problem still persists. Please help.

PTMensah said:
the touchscreen of my samsung galaxy SL i9003 stops responding about 5 seconds after i unlock the screen.
I have done factory reset but problem still persists. Please help.
Click to expand...
Click to collapse
Is your phone in warranty?

can you give us some basic information? such like rom & kernel version, wether you rooted and ade using cputuningtools or something like that.
if you are under stock rom(original samsung & all further updates over kies) and u have done nothing unnormally so far i would recommend use the warranty too; )
Sent from my GT-I9003 using XDA

thanks guys
i have not rooted or changed the stock rom
i only factory reset it when the problem started
i just discovered that when i plug in the charger the touch screen works normally but does not respond to touch when not charging

PTMensah said:
thanks guys
i have not rooted or changed the stock rom
i only factory reset it when the problem started
i just discovered that when i plug in the charger the touch screen works normally but does not respond to touch when not charging
Click to expand...
Click to collapse
I had the same issue. I got my touch panel replaced by the Samsung guys. That's why I was asking whether your phone is under warranty or not.
Sent from my SIII looking SL
....
...
I'm more on XDA than FB...

Here we go, this proves this has nothing to with CM9, this guy is on stock.
Many people are blaming CM9 for this and claiming it caused the problem.
It's a hardware defect.

Skander1998 said:
Here we go, this proves this has nothing to with CM9, this guy is on stock.
Many people are blaming CM9 for this and claiming it caused the problem.
It's a hardware defect.
Click to expand...
Click to collapse
Agree. :good:
I'll wait for a few weeks or till the phone is usable for the kernel 3.0. :fingers-crossed:
If not then no other option but create a Rs.5000 hole in my pocket. :crying:

Same case with me... Bought the i9003 March 2011.
I'm on DDKP3 and around the same time as the OP, my touchscreen started to act strange... responsive only when charger is plugged in. Tried factory reset, but problem came back after some hours!
If this is a product-wide issue, then I guess sammy should replace it for free, even if it's out of warranty... too busy to go to the nearest service cenrter, will check later.
Till then, please keep me updated how it goes for you.
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
Just wondering, if a reflash of DDKP3 via ODIN or any custom ROM would solve the issue... please suggest.

I guess the sensitivity settings (or something like that) has changed without you knowing. Don't know if it is the same as s2 but in s2, sensitivity of the phone not plugged in the charger and plugged in has different settings. So maybe the settings for it in your case (unplugged) has changed but not on the plugged in settings. It's all in the kernel btw.
Sent from my GT-I9100 using xda premium

^^^ So what do you suggest?

agnivo007 said:
^^^ So what do you suggest?
Click to expand...
Click to collapse
Maybe asking a kernel dev if the values changed or what not. If i'm correct then it's a software problem, if not then maybe a hardware problem.
Sent from my GT-I9100 using xda premium

Same problem!!!
It happened last week when my phone surprisingly started showing this problem. After unlocking the phone the screen becomes unresponsive. In my case it is just 1-2 secs after unlocking the phone.
It lasted for a day, I tried flashing different ROMs. I was on XXKPE when it happened. And than suddenly my phone started working fine until yesterday when this thing again happened and the problem still persists (I am still on KPE). I dont know what to do.
I think it can be some software problem as the screen and touch keys do work for some time before becoming unresponsive and even the logcat shows no problems for the touch screen. I am going to try more ROMs now. Will keep you posted.

Possible solution !!!
Friends, I think I found a possible solution for this issue. Though it seems to work for me... I have to keep the phone under observation for some days until I can say it's the final solution.
A similar thread: http://forum.xda-developers.com/showthread.php?t=1695149
The possible cause for the touch screen going unresponsive seems not to be a hardware/software glitch; but environmental issue! And it doesn't depend on the ROM your'e running.
I noticed that most people from India having this issue say that this problem started in June, when the rainy season starts and it gets humid and damp.
In fact my phone showed this issue when it had rained for the last 2 days and it was very damp and humid inside the house.
You can do the following:
1. Take out the back cover, memory card, SIM and battery.
2. Place the backside of the phone near a hot air source (on top of a running CRT TV/monitor, hairdryer, laptop fan vent) for sometime.
3. Reassemble and check if the problem has gone away.
Do not panic if the handset gets a bit hot in the process!
In my case, I left it on the top grille of a CRT TV for a day which ran for 8hrs.
Do let me know if this works for you...

Flashing the ROM does not solve the problem
neetinnagap said:
It happened last week when my phone surprisingly started showing this problem. After unlocking the phone the screen becomes unresponsive. In my case it is just 1-2 secs after unlocking the phone.
It lasted for a day, I tried flashing different ROMs. I was on XXKPE when it happened. And than suddenly my phone started working fine until yesterday when this thing again happened and the problem still persists (I am still on KPE). I dont know what to do.
I think it can be some software problem as the screen and touch keys do work for some time before becoming unresponsive and even the logcat shows no problems for the touch screen. I am going to try more ROMs now. Will keep you posted.
Click to expand...
Click to collapse
I've sent the phone to the samsung guys who have flashed the phone twice but the problem still persists.

PLs keep us updated
agnivo007 said:
Friends, I think I found a possible solution for this issue. Though it seems to work for me... I have to keep the phone under observation for some days until I can say it's the final solution.
A similar thread: http://forum.xda-developers.com/showthread.php?t=1695149
The possible cause for the touch screen going unresponsive seems not to be a hardware/software glitch; but environmental issue! And it doesn't depend on the ROM your'e running.
I noticed that most people from India having this issue say that this problem started in June, when the rainy season starts and it gets humid and damp.
In fact my phone showed this issue when it had rained for the last 2 days and it was very damp and humid inside the house.
You can do the following:
1. Take out the back cover, memory card, SIM and battery.
2. Place the backside of the phone near a hot air source (on top of a running CRT TV/monitor, hairdryer, laptop fan vent) for sometime.
3. Reassemble and check if the problem has gone away.
Do not panic if the handset gets a bit hot in the process!
In my case, I left it on the top grille of a CRT TV for a day which ran for 8hrs.
Do let me know if this works for you...
Click to expand...
Click to collapse
Thanks.
Pls keep us updated

Problem Solved!!
Thanks to agnivo007.
I guess the climate is the only reason. I used his method to heat up my phone a little bit by charging it enough. Than it started working fine. No problems since then. Lets see.

ephraim033 said:
I guess the sensitivity settings (or something like that) has changed without you knowing. Don't know if it is the same as s2 but in s2, sensitivity of the phone not plugged in the charger and plugged in has different settings. So maybe the settings for it in your case (unplugged) has changed but not on the plugged in settings. It's all in the kernel btw.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
But changing the panel solves the issue..
The kernel won't reset itself if you change the screen.

Skander1998 said:
But changing the panel solves the issue..
The kernel won't reset itself if you change the screen.
Click to expand...
Click to collapse
ephraim033 said:
Maybe asking a kernel dev if the values changed or what not. If i'm correct then it's a software problem, if not then maybe a hardware problem.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Sent from my GT-I9100 using xda premium

Touch Screen non-responsive Problem
I had the same issue and when i dismantlement the thing, came across a small batter. could this be the reason? Cos while charging this battery is not used but when running with battery, this small dry typed batter can be in use.

Found Any Solution
Could any 1 find a solution for this matter?
If so pls. update. Mine is still there.
I can't get rid of it.

[Q] Nexus 5 isnt booting

Hi, i got a huge problem with my nexus 5.
A few days ago i dropped my phone whereby the screen cracked but it was still working. Over the next days the screen went black more frequently.
At some point the whole nexus stopped working and now it is just vibrating and heating up when i try to boot. Seriously, there is nothing to see on the screen.
pls tell me if forgot certain informations which can be helpful for you
OS: CM11

It's almost certainly a hardware problem, but try flashing the factory image. If that Durant work it's hardware. Could be a loose connector or something more serious.
Sent from my Nexus 9 using XDA Free mobile app

Hardware Gurus: is this a hardware problem?

Hi guys
I'm sure this problem is not brand specific but a general issue:
My device (Xiaomi Redmi Note 1W 3G) loses its display from time to time. The screen (1) flickers for a few secs or
(2) during standby it loses power, only way is reinsert battery. Sometimes there is a freeze (3)which means for half a minute the system hangs until it reboots all alone.
My question to you: is it possible some internal wires have become loose, or and other idea?
btw, my device never ran correctly, from the first day on, issues.
So far, I've tried a custom ROM and several global versions as well as TWRP and CWM.
Any help highly appreciated! [emoji316] [emoji26]
tapatalked

TalkingHeadAche said:
Hi guys
I'm sure this problem is not brand specific but a general issue:
My device (Xiaomi Redmi Note 1W 3G) loses its display from time to time. The screen (1) flickers for a few secs or
(2) during standby it loses power, only way is reinsert battery. Sometimes there is a freeze (3)which means for half a minute the system hangs until it reboots all alone.
My question to you: is it possible some internal wires have become loose, or and other idea?
btw, my device never ran correctly, from the first day on, issues.
So far, I've tried a custom ROM and several global versions as well as TWRP and CWM.
Any help highly appreciated! [emoji316] [emoji26]
tapatalked
Click to expand...
Click to collapse
Screen flickering issues seem to be common in the Redmi Note series :/... I read that someone who had this problem found that factory reset fixed it, but once he entered recovery the issue came back. I would assume it's a hardware problem with my experience with laptops and desktops (yes they aren't phones though). I don't think that there's a wire that's loose; I think it's something on the motherboard causing the problem, not the screen panel itself. Can you send it back to the person you bought it from and get a replacement?

Thanks for your reply. I've never read about these issues anywhere before, but now I see that this might be Xiaomi's fault. Nonetheless I'm gonna open it up just to check it out as I imported my Note from China. Sending it back would be way too adventurous.
I'll turn my back to Xiaomi, other brands are smaller yet more reliable.
tapatalked

[Completed] Galaxy S5 plus problem!!

I have purchased a galaxy s5 plus 3months ago. And for a week now, it started doing this weird thing! Almost everytime I try to unlock the phone, the screen flickers a yellowish tint. Sometimes it takes 2 or three tries to get the device to display correctly. there are times when it flickers and goes blank, then I'd have to lock and try again a couple of times, and other times it just flickers and displays correctly right after. The problem never occurs while using the device, only on unlocking.
I wonder what the cause might be. And if anybody had a similar experience and has a fix, please help!
My galaxy s5 plus (sm-g901f) runs on android lolipop 5.0.2.

OthmaneQ said:
I have purchased a galaxy s5 plus 3months ago. And for a week now, it started doing this weird thing! Almost everytime I try to unlock the phone, the screen flickers a yellowish tint. Sometimes it takes 2 or three tries to get the device to display correctly. there are times when it flickers and goes blank, then I'd have to lock and try again a couple of times, and other times it just flickers and displays correctly right after. The problem never occurs while using the device, only on unlocking.
I wonder what the cause might be. And if anybody had a similar experience and has a fix, please help!
My galaxy s5 plus (sm-g901f) runs on android lolipop 5.0.2.
Click to expand...
Click to collapse
Hi, Thank for using XDA assist It looks like there is no dedicated forum for your device, however
There is a general forum for android here http://forum.xda-developers.com/android/help where you can try to ask to get expert's help.
Good luck.

S6 Freeze/bootloop out of the blue

So had this phone for a while now and no problems, been running nougat for the past few months, this morning took my phone off charge and placed in pocket. A bit later I checked my phone, it was not responsive a black screen, did a hard reset does the samsung logo then gets stuck either flashing blue or pink. So leave it until I get home, flash latest nougat with odin installs fine, reboots and does same thing freezes at boot samsung flashing blue. Flash it again and now its froze after its said erasing...
I think something has failed hardware wise, any others had this issue?.

ellis4567 said:
So had this phone for a while now and no problems, been running nougat for the past few months, this morning took my phone off charge and placed in pocket. A bit later I checked my phone, it was not responsive a black screen, did a hard reset does the samsung logo then gets stuck either flashing blue or pink. So leave it until I get home, flash latest nougat with odin installs fine, reboots and does same thing freezes at boot samsung flashing blue. Flash it again and now its froze after its said erasing...
I think something has failed hardware wise, any others had this issue?.
Click to expand...
Click to collapse
Just install "CPU awake" from play store, this will help you keep the device working, this problem is very common in each & every Samsung flagship, starts after 2 year use(won't ever buy a Samsung flagship again), no fix for it, if you don't believe me, check Evey flagship forum q/a section.

rifek4 said:
That app is useless, in that case completly useless. That app just won't allow CPU's get to deep sleep. But in him case that looks like just next S6 who get hardware broken from unknown reasons
Click to expand...
Click to collapse
Really? I have a note 4 , exactly same problem, that app gave it new life & not just mine, many note 4 users are using it who are facing the same problem, so, next time instead of just posting nonsense, do some research.

rifek4 said:
He even cannot turn on the phone, maximum what he can see is SAMSUNG logo so what the **** you are talking about turning on some app on working system?
Click to expand...
Click to collapse
That's a nand problem, if the device is cooled (I hold mine in front of AC for 5min.), that will help it to turn on & once it's on, install the app & it will work fine but it shouldn't be allowed to shutdown or it has to be cooled down again, it's not a new problem, thousands of Samsung mobiles which ship with faulty nand face the exact same problem, I know it sounds silly, it is what it is & it works(for thousands users)

rifek4 said:
Never before heard bullshits like that. Can you give some link to any information which will confirm that what you told so that a CPU Awake app will fix broken Samsung device? Please about it.
P.S.
I could'nt find anything about it :laugh:
Click to expand...
Click to collapse
Enough with your bull****, here, take a look...
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
Read it, on almost every page someone recommended using cpuwake, it's not my problem that you are such a fool who instead of trying to help someone with some advice, would just bash other people who have faced similar issues & maybe know the solution. You can go **** yourself for all I care.

Rishi is correct about cpu awake on the Note 4. It is commonly viewed as a means of extending the life of the Note 4 but eventually the phone will fail.
Sent from my SM-G920W8 using Tapatalk

ellis4567 said:
So had this phone for a while now and no problems, been running nougat for the past few months, this morning took my phone off charge and placed in pocket. A bit later I checked my phone, it was not responsive a black screen, did a hard reset does the samsung logo then gets stuck either flashing blue or pink. So leave it until I get home, flash latest nougat with odin installs fine, reboots and does same thing freezes at boot samsung flashing blue. Flash it again and now its froze after its said erasing...
I think something has failed hardware wise, any others had this issue?.
Click to expand...
Click to collapse
i am experiencing the same problem did you find any fix for this problem plz help anyone

Navedsid said:
i am experiencing the same problem did you find any fix for this problem plz help anyone
Click to expand...
Click to collapse
Unfortunatly not, sold the phone as faulty as don't want to throw money at it, will not be getting another s6 my worse samsung yet, meanwhile my note 3 is still working great and will do for now.