Database Develop

[Q] Please help: trackball constantly registering clicks even if not pressed

Hey guys
I tried to search but I haven't found anyone with this particular problem:
Today I had to swap the SIM card on my dad's N1. I must have touched something the wrong way since after doing so, it seems the trackball is constantly being pressed (even though it's not).
Here's some of the consequences of this, that are making me literally freak out:
1. I can't get into recovery (as soon as I do, a click is registered on "Reboot phone).
2. It only boots in safe mode
3. Navigating around the phone is almost impossible, opening up the app drawer immediately launches an app.
By hitting a text input field, I can observe how it's registering clicks really fast (by observing how the whole text field is selected/deselected)
I tried fiddling a bit with the trackball, long pressing it, clicking it, etc, but it's still a no go (long pressing it does register as a long press, but as soon as I let go, the constant clicking continues)
Seeing as how this happens whether or not after the ROM has booted, it looks like this is a hardware problem.
Has anyone run into something like this before? Any ideas on how to fix this myself?
I don't know if sending it to HTC is an option because of two reasons:
1. I live in Costa Rica, don't know if there's HTC support here, or if it'd be safe shipping the phone to the states for a repair.
2. My dad's N1 is rooted, but bootloader hasn't been unlocked. It's running a custom rom. Right now I'm not sure if I can't get it back to stock since I can't even get into recovery.
Please help! Thanks

I had this exact problem for about a day or so it turns out I had got the trackball wet try clicking it and rolling it also try giving it a day or two it might just come back good luck on your nexus
Sent from my Nexus One using XDA App

Turns out you were right!
I left it sitting for a day, turned it on and the problem was still there. I got a hair dryer and used it on the phone for like a minute, turned it on, and all is good now!
Thanks!

Problem has come back and won't go away now... definitely looks like a hardware issue, will call HTC support.

[Q] Lagging or weird hehavior found on my buttons

I have been having this weird problem for over a month now.
Virtual Button gets stuck as if im touching it rapidly. it happens randomly too. for example, after a reboot i was using xda app. After hitting "back" button, its button backlight goes off and doesnt respond. Everything else still works but the button gets stuck like that for 20second.
Sometimes when im watching a movie without hording it, quick option pops up as if i have pressed the button next to home button.
anyone else with this issue???
I have 2.1 stock rom uptodate with kies, ryan lag fix, and realook screen protector on it.
Sent from my GT-I9000M using XDA App

josb0513 said:
I have been having this weird problem for over a month now.
Virtual Button gets stuck as if im touching it rapidly. it happens randomly too. for example, after a reboot i was using xda app. After hitting "back" button, its button backlight goes off and doesnt respond. Everything else still works but the button gets stuck like that for 20second.
Sometimes when im watching a movie without hording it, quick option pops up as if i have pressed the button next to home button.
anyone else with this issue???
I have 2.1 stock rom uptodate with kies, ryan lag fix, and realook screen protector on it.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
This just started happening to me (literally 15 seconds ago) and I want to find out what's going on.

+1
same thing happens to me. But after pressing the central button, the buttons reappear. strange weird
I do not install any lagfix or change the rom, I have my Samsung Galaxy S as a wine factory

I just started to have exactly the same issue with my Vibrant.
Any follow up on this?

Well, one thing i wanna ask you guys is that how many apps do you have installed on your system? Im actually having less of this symptom these days as i have uninstalled dozens of software. Not sure if that was the issue tho.
Sent from my GT-I9000M using XDA App

I deleted few apps which I installed in last few days and so far so good....but its just few minutes of use yet!
Specifically deleted "Noled".

Still getting lag with BACK button. Though it happens once or twice a day....very weird!
I have been using Samsung Vibrant for 3 months now and this problem just started two days back.

I'm having problems with buttons going off by themselves now. Browsing the internet or writing a message, the menu pops up by itself; Its annoying and its starting to get worse. I'm starting to wonder if I should trade in my phone; this is my third phone.
// galaxy s

I too have this exact same issue with my i9000m. Stock rooted rom with voodoo lagfix. Uninstalled everything, factory reset, clear cache, unroot - nothing fixes it. I have a replacement phone on backorder that will be replaced no questions asked thankfully.
Sounds like it's a somewhat common problem.

now this is getting irritating! seems like an issue with only Bell version I9000M. Couldn't find this problem any where else on web.

did a hard reset and before loading any apps..... played around with phone and found the same lag with back button!

After looking at your replies, it seems like these two factors are causing this strange button lag:
+Bell Mobility
+2.1 Éclair
Can we confirm please? Are you all using Bell & 2.1 with the issue?
Hopely Froyo can fix this issue. My phone was alright for couple of weeks but it came back worse than ever!
I’m starting to hate Samsung more than ever for the lag of updates & lies.

it might be only with some phones
i'm on i9000m as well, 2.1 stock, but i do not have the button problem you guys are describing.

AllGamer said:
it might be only with some phones
i'm on i9000m as well, 2.1 stock, but i do not have the button problem you guys are describing.
Click to expand...
Click to collapse
AllGamer, I think you're the lucky one when it comes to your Galaxy. I'm curious if this issue happens to phones running custom roms or the official froyo release.

On stock firmware i9000m and OCLF with root. Im getting a huge lag (10-15 seconds) whenever I hit my home button. Using launcher pro but the problem only popped up yesterday.
Checked watchdog and it only shows 4mb free BUT task manager shows 65mb free. Any thoughts?
Sent from my GT-I9000M using XDA App

You're not the only ones with the issue. Look at this guy using a Bell SGS on youtube (apologies if this is one of you guys )
http://www.youtube.com/watch?v=JBe0txXobwY
Also, its not just the Bell SGS, my AT&T Captivate does it on the Menu key and its very very annoying. Theres a similar thread in the captivate forum and no doubt, on in every SGS forum as they all use the same touch panel.
If its very common, which seems to be the case, could it be related to dust ingress into the touch panel?

Disabled Quickdesk (glcery handy app), left the office early, and now everything works great. Not sure which one worked....
I was getting a black screen for 5-10 seconds every time i pressed the home button. Anyone else with quickdesk issues? Suggestions?
Sent from my GT-I9000M using XDA App

I factory reset my phone and then un-rooted it just for the sake of testing out some ideas. It didn't help at all and the problem persisted for awhile until I found something interesting;
If you are having the buttons 'stick' or malfunction, go to recovery mode via 3-button. Once you are in there, start pressing your soft keys (I did this for 10 minutes straight when my buttons were sticking).
Tell me how your buttons respond, do they stick or not? We could determine if it's software or hardware.

hol17 said:
I factory reset my phone and then un-rooted it just for the sake of testing out some ideas. It didn't help at all and the problem persisted for awhile until I found something interesting;
If you are having the buttons 'stick' or malfunction, go to recovery mode via 3-button. Once you are in there, start pressing your soft keys (I did this for 10 minutes straight when my buttons were sticking).
Tell me how your buttons respond, do they stick or not? We could determine if it's software or hardware.
Click to expand...
Click to collapse
I thought the buttons didnt respond in recover mode...

They light up and respond to touches; if you press the menu key it actually removes and restores the recovery screen.
Sent from my GT-I9000M using XDA App

[Q] Soft Keys Not Working

This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?

Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs

That is definitely not normal behaviour.

Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s

hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.

any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^

I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department

I have the same problem its almost like the soft key is being held down, anyone find a fix for this?

Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!

robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.

I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.

cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.

I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.

Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492

^^^
Do not do this unless you have a i9000m. You will break your buttons.

electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...

[FIX][08.04.2011]Patch for "Screen won't come on after device wakes" (RHO_S2_00895)

[FIX][08.04.2011]Patch for "Screen won't come on after device wakes" (RHO_S2_00895)
Problem: Device doesn't come back from suspended mode. Pressing the power button, sliding out the keyboard or taking out the stylus does nothing.
Occurrence: Random.
Quick fix: None known.
Request: Kinda all over the Rhod forums.
Affected ROMs: HTC Stock S2 2.07, all custom roms based on 2.07 drivers. Probably 2.10 drivers are partly affected too.
Patch:
For stock roms (standard HTC patch package, .exe)
For custom roms (download this if you're unsure, works for stock roms too)
For cooks (extract and put into OEMDrivers)

Thanks!
Let's see (in time) if the SOD's are finished for us.

HRQ.SLV said:
Thanks!
Let's see (in time) if the SOD's are finished for us.
Click to expand...
Click to collapse
It must be a matter of settings or hardware, I never suffered from SoD.

Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
That's because youre a great cook!
This thread should be sticky...

HRQ.SLV said:
That's because youre a great cook!
This thread should be sticky...
Click to expand...
Click to collapse
Not only this one should be sticky...

.......Done

Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.

It doesn't work for me either
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G

Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
Thanks for sharing...I have had SOD only with certain builds...its been a while since I had one...

KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.

That would be my [email protected] cable....
KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse

bisanti said:
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G
Click to expand...
Click to collapse
The exe file (for stock roms) is intended to work on Europe roms. I have no knowledge of HTC releasing this patch for other regions.
It's no fix for any problem with the phone The patch doesn't even touch the backlight thing.

Jackos said:
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.
Click to expand...
Click to collapse
It happens all the time. I turn the phone on via the power button. Boots up. Let it sit till backlight goes off. Press power button, nothing happens.
I can turn the phone on, press the power button to turn the backlight off and when I press it again, nothing happens.
Wild Child said:
That would be my [email protected] cable....
Click to expand...
Click to collapse
I do not think it's a flexcable problem. If I can turn the screen off and power on the device with the 'power button', it has to be something software.
I have to check again if the device comes back on, but with really really low backlight.
It's annoying, I have to restart to see a text, missed call, etc.
Thanks for your help so far.

Won't wake up
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)

pbarschall said:
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)
Click to expand...
Click to collapse
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.

Jackos is this in your ROM? I have found several times my TP2 needs a reset as the power button does not bring it life. If I take the stylus out (when this happens) the row of keys light up, but still the display is blank. I assume it's already in your ROM (Jackos S3 1.1.2 SleekBASIC) otherwise I would have installed it.

It's going to be included from version 1.1.3 and up.

Jackos said:
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.
Click to expand...
Click to collapse
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. Apparently being for Europe it has corrupted my phone and none of the talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.

scottandmo said:
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. No talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.
Click to expand...
Click to collapse
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.

Jackos said:
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.
Click to expand...
Click to collapse
Deleting the HtcPm.dll and rebooting fixed it, Thanks! I'm assuming that won't have any other side effects...

touch screen not responding

I read already that a few ppl had this problem with different ROMs. I never had it before today. I switched the screen on and it looked normal but I couldn't do anything. I could swich the screen off again and tryed to press the power button long, OK shoutdown menu apeared but as the touch screen didn't respond I couldn't select anything. Well I pulled the battery out and it started normal, works good again.
Maybe I never have this problem again, but if it apears again might canging the kernel help or is it a ROM problem? I had this problem with JellyBam 4.1 so I could just use a different CM10 kernel.
BTW as I pulled the battery I have no log, but there might be a change to still get that log with ADB because the phone was still running just no touch response and that means (nearly) unuseable. I just have no clue how to do it, if it is posible could somebody tell me how to get that log?

Before pull out battery, try hold both Vol + and Power button until the phone restart (if it can, if not, then, you can pull out battery and forget the logcat ^^)

SaschaKH said:
I read already that a few ppl had this problem with different ROMs. I never had it before today. I switched the screen on and it looked normal but I couldn't do anything. I could swich the screen off again and tryed to press the power button long, OK shoutdown menu apeared but as the touch screen didn't respond I couldn't select anything. Well I pulled the battery out and it started normal, works good again.
Maybe I never have this problem again, but if it apears again might canging the kernel help or is it a ROM problem? I had this problem with JellyBam 4.1 so I could just use a different CM10 kernel.
BTW as I pulled the battery I have no log, but there might be a change to still get that log with ADB because the phone was still running just no touch response and that means (nearly) unuseable. I just have no clue how to do it, if it is posible could somebody tell me how to get that log?
Click to expand...
Click to collapse
same problem for me...i thouht it is my screen problem..bcoz when i hold n press the area near the front facing camera then the touch again becomes normal fo me...

SamBG said:
same problem for me...i thouht it is my screen problem..bcoz when i hold n press the area near the front facing camera then the touch again becomes normal fo me...
Click to expand...
Click to collapse
If it happens again I will try if that does anything but I doubt it because not even the 4 touch keys did work.

have this problem to..any solution for this?its really suck,but sometimes when i use in recovery with cable connect to laptop its work for a moment,but suck again when unplug the cable.

SaschaKH said:
I read already that a few ppl had this problem with different ROMs. I never had it before today. I switched the screen on and it looked normal but I couldn't do anything. I could swich the screen off again and tryed to press the power button long, OK shoutdown menu apeared but as the touch screen didn't respond I couldn't select anything. Well I pulled the battery out and it started normal, works good again.
Maybe I never have this problem again, but if it apears again might canging the kernel help or is it a ROM problem? I had this problem with JellyBam 4.1 so I could just use a different CM10 kernel.
BTW as I pulled the battery I have no log, but there might be a change to still get that log with ADB because the phone was still running just no touch response and that means (nearly) unuseable. I just have no clue how to do it, if it is posible could somebody tell me how to get that log?
Click to expand...
Click to collapse
This appears to be a common P970 bug with 4.04+ ROMS. Loss of touch control, and long-pressing the power button brings up the shutdown menu which you can't access.
GB/2.3.4 ROMs don't have this bug. I'm not aware of any fix, save reverting to GB.

androcraze said:
This appears to be a common P970 bug with 4.04+ ROMS. Loss of touch control, and long-pressing the power button brings up the shutdown menu which you can't access.
GB/2.3.4 ROMs don't have this bug. I'm not aware of any fix, save reverting to GB.
Click to expand...
Click to collapse
OMG somebody is still replying to that old post, over a year old, I don't even use that phone anymore, may last year I got my S3.
As I said, it only happend to me once with the JellyBam 4.1 ROM, I didn't gave to mutch to that problem with JellyBam, cause it was not the only one. That ROM was bs and didn't stayed long on my phone. It had everything, but nothing worked.
A lot GB and ICS ROMs worked well and even most of the CM ones worked rather good, they where just to power hungry. I liked all the Zeus ROMs, especially IZS. IZS is LG 4.0.4 based and was by fare the one I liked the most.

SaschaKH said:
OMG somebody is still replying to that old post, over a year old, I don't even use that phone anymore, may last year I got my S3.
As I said, it only happend to me once with the JellyBam 4.1 ROM, I didn't gave to mutch to that problem with JellyBam, cause it was not the only one. That ROM was bs and didn't stayed long on my phone. It had everything, but nothing worked.
A lot GB and ICS ROMs worked well and even most of the CM ones worked rather good, they where just to power hungry. I liked all the Zeus ROMs, especially IZS. IZS is LG 4.0.4 based and was by fare the one I liked the most.
Click to expand...
Click to collapse
I shouldn't have replied to you. It's an old post. I should have targeted the latest post in the thread.

i think its hardware issue,,if i press and hold a little while on upper screen (right beside lg logo) touch screen became normal again. but sometimes need to hold on there when touch not work again. a member on this forum call it a flex issue of the touchscreen.
anyone know how much cost to replace it with new flex to fix this issue?