Database Develop

Problem with Notification Bar.

I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)

Where do you live? I live in florida, and this happens to me when I'm outside for an extended period on a really humid day. Once I take it in to the ac for a few, it's all ok.
Sent from my HTC Hero CDMA using XDA App

Louisiana. Doesn't seem like that would be it though. My wife has the same phone and has never experienced this problem (she has OEM 1.6 version). I am leaning towards software issue.

mar122999 said:
I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)
Click to expand...
Click to collapse
You posted this in the wrong forum
Anyway, it could be a hardware problem, but it sounds more like a software issue. Sometimes this happens to me when the phone slows down. Are you low on RAM when this happens?

Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?

mar122999 said:
Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?
Click to expand...
Click to collapse
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.

derekwilkinson said:
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.
Click to expand...
Click to collapse
+1
when i had one on my phone it would do this. i think its static tricking the touchscreen.

[Q] Erratic Touchscreen Issues

No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.

have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk

Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.

angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?

dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!

angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.

bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.

I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.

I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.

I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.

queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!

[Q] Phone Unresponsiveness

Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.

Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10¢ apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk

I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium

I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.

What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App

revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.

I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.

Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.

Droid4 Stock ICS Bugs

All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)

The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:

podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?

I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?

podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS

I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app

danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:

I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol

One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.

I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!

I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.

podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.

Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...

podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.

podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.

danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so

Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:

danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.

I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?

I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?

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