Touch Screen Not Responding - Captivate Q&A, Help & Troubleshooting

So I am having a bad problem with my i896. The other day I tried to install a beta version of XBMC. Of course it didn't work. It got so bad that I had to do a factory reset and reinstall CM9 (the latest nightly build).
So that worked OK for a few hours, then all of a sudden, the touch screen just stopped responding. I've tried doing another factory reset and reinstalling CM9 again, no luck. I am really hoping that it isn't a hardware problems.
Any suggestions?

You can try flashing stock, if it still doesn't work your digitizer probably went bad. You will have to have it replaced or search how to do it yourself. Ebay has them pretty cheap.
Sent from my SGH-I897 using xda premium

I know this i a liitle old of a thread but instead of starting new one i will ask my simple question here. I need to replace the screen/digitizer on a rogers I896. will this work or is the i896 and i897 so different that it will not?

Grondinm said:
I know this i a liitle old of a thread but instead of starting new one i will ask my simple question here. I need to replace the screen/digitizer on a rogers I896. will this work or is the i896 and i897 so different that it will not?
Click to expand...
Click to collapse
That would be a trueselo question since he seems to know more about rogers captivate then anyone I've seen
Sent from my SGH-I897 using xda premium

Maybe
cgulka said:
So I am having a bad problem with my i896. The other day I tried to install a beta version of XBMC. Of course it didn't work. It got so bad that I had to do a factory reset and reinstall CM9 (the latest nightly build).
So that worked OK for a few hours, then all of a sudden, the touch screen just stopped responding. I've tried doing another factory reset and reinstalling CM9 again, no luck. I am really hoping that it isn't a hardware problems.
Any suggestions?
Click to expand...
Click to collapse
Try flashing stock

Related

Phone often freezes with froyo ....keep having to pull battery

What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App
Anyone?
-------------------------------------
Sent via the XDA Tapatalk App
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?
Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.
Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App
I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App
SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.

Cannot Connect to Camera, Cyanogenmod 6.0 rc1

I was using my phone today, and my camera worked just fine, i took a couple pictures with it. then later on in the day, the camera app didnt work, as i clicked the app it would just make the screen black, and would take a little while to boot up the home screen if i pressed home. after a while it would as me to force close, and it would say that it couldnt connect to the camera.
Please help, Thanks in advance.
EDIT: Flashed wildmonks 2.6.35 kernels (considered a work-in-progress, personally tested on cm6 RC1 and Nightly) it worked but then the problem arrived, i restored my nandroid backup i had done prior to flashing the kernel, and the camera still doesnt work.
I had this exact same problem and had to send my n1 back to htc for hardware failure. A bunch of threads like this in the offical nexus one forums at google too.
Too bad your boot loaders unlocked. i sent mine back stock.
darn so its a hardware failure? is there any way to be sure?
SplitSnake said:
darn so its a hardware failure? is there any way to be sure?
Click to expand...
Click to collapse
try nan restore? or flashing another rom?
reflashed my nexus one with rodriguezstyle CM6 limemod. the camera still isnt working. what to do if i was sold this with an unlocked bootloader?

[Q] Stuck on bootscreen

Got a galaxy s gt-i9000 which I got in Italy, since it was full of crappy apps in Italian I couldn't delete (and I mean really FULL), I tried rooting it. Since it was a "JPP", there was no easy way to do this. I tried this topic randomshouting.com/2011/02/20/How-to-root-and-unlock-the-samsung-galaxy-s-jpp-build.html and that's where things went wrong.
Any help on how to get back to a working phone would be much appreciated! I can enter download mode and tried a couple of things, but nothing worked.
Try this
http://samsunggalaxysforums.com/showthread.php/2921-How-to-use-Odin-to-upgrade-to-Froyo-from-Eclair
Sent from my GT-I9000 using XDA App
I used the one for when you already were on JPA (since I remembered flashing to that), and it worked. I still have voodoo on there, so I might need to flash again somewhere in the future, but for now, I'm happy. Moreover, I also finally got it rooted. Thanks!

Some Roms just won't flash.

Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Maybe he dont follow the instructions correctly
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
What method is he using to flash? If using pc Odin does the flash get stuck at factoryfs. Img?
Was he on ics stock and did he perform any factory resets on it?
If answers are yes, it's likely he's got traces of damage on his emmc chip, but we need to know where the flash is failing to understand further.
Sent from my GT-N7000 using xda premium
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
meminiau said:
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
Click to expand...
Click to collapse
Try flashing rom with pc odin instead of cwm.
Check out Dr ketan sticky thread in rom development for directions on how to use pc odin. It's simple.
Let us know how you progress.
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
No problem at all.
Sent from my GT-N7000 using xda premium
What?????
Swiped on my Gnex
Sounds very odd - only though is he's not following instructions correctly..

[Q] I957 ATT , touch screen not working after ICS upgrade

Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
wamaOnline said:
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
Click to expand...
Click to collapse
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
jd1639 said:
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
First was this one sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=XXX&os=1&type=3#firmware[/url]
Then when it didn't work, tried this one
sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=ATT&os=1&type=3#firmware
Sorry for the strange URL format, but seems as anew member I don't get to add URLs yet
orlandoxpolice said:
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sorry, I meant the cwm recovery was flashed correctly and functioning
Btwi tried the fix permissions suggestion from the similar thread but no luck
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
jd1639 said:
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
It is the Odin version I have used,
One more note now, am not sure if that is normal if not.but after the latest flash ( preceded by a data wipe and format ) I can now see zip file I have placed on sdcard but can't access them for flashing and/or ad new zip files from pc
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried,booted, "SAMASUNG"screen only ( as expected sicne i formatted the system ), then re-flushed the ATT ICS and same output
Am trying to get a new ROM flashed, but when the device powers up [ without me going through the wizard ], i can't write anything to SD from my PC.
Any info around here about flashing CM or AOKP using ODIN for this I957 ?
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
I'm at a loss, you've tried everything that has gotten me beyond the boot screen.
Anyone else have any ideas?
Sent from my SGH-I727
wamaOnline said:
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
Click to expand...
Click to collapse
I should mention something that has gotten me worried, i flashed a TWRP recovery to check if the touch would work there, but it didn't.
Not sure if i should be worried about HW now, or try another TWRP for instance? Or perhaps TWRP shares another flawed tab wide configuration with the Android image ?
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Then why is it still borked when reverting to hc?
Sent from my SAMSUNG-SGH-I727 using xda premium
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
jd1639 said:
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
Click to expand...
Click to collapse
yea i dont get how a rom flash could cause a hardware issue
orlandoxpolice said:
yea i dont get how a rom flash could cause a hardware issue
Click to expand...
Click to collapse
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
wamaOnline said:
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
Click to expand...
Click to collapse
Got it Reassembled and cleaned it and it worked
same prob, touchscreen not responding
wamaOnline said:
Got it Reassembled and cleaned it and it worked
Click to expand...
Click to collapse
I'm having this issue of the touchscreen not responding on my s2 now
You say you got it reassembled? What did you have to do to repair it
any help greatly appreciated
I have JB 4.1.2 and cwm 9.1 flashed
after reboot screen comes on but won't respond to touch, I can only access download and recobvery screens
I also have the phone not showing on computer when usb attached but am loading rom etc to ext sd card first and installing them from cwm
Got the maintenance center to disassemble it, clean the pins and reconnect the screen and then it worked
Sent from my LT26ii using xda app-developers app

Categories

Resources