[Q] Soft Keys Not Working - Galaxy S I9000 Q&A, Help & Troubleshooting

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...

Related

Hard Reset not working?

Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Dr. Strangelove said:
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Click to expand...
Click to collapse
Few Tricks, Make sure you are not plugged in USB. Make sure you are not "fat fingering it." Some people use chopsticks to be sure. And Hold it for long after the Screen goes Black.
Believe me, I've already tried the things you said.
Although I successfully mananged in the past to hard reset my phone, I checked the threads and the following vid:
How To Hard Reset Kaiser:
http://www.youtube.com/watch?v=fZPzT_L2FZQ
Usually I am the problem, but this time I can't figure out what I'm doing wrong.
Just wondering:
Which part of the Phone (ROM) is in control of the Hard Reset part? (e.g.: Bootloader, Radio Rom, Regular Rom,...)
Use "Clear Storage". It does the same thing.
Also, JM is most likely correct. It is most likely an issue of how you are pushing the buttons. Make sure you hold only ythe soft keys first, using your fingernails, then push the reset tab on the bottom & hold it. Don't just push the reset & release, but keep it held down.
Based on your previous message about your phone being haunted - mine is too btw, I think it's because the soft buttons aren't being acknowledged by the OS - which implies some REAL big problems.
I took mine back to the T-Mobile store today where I got told that it needs to be sent back to their workshops to fix it... and then got told that "mostly they just send out a new phone".
My phone is exhibiting the following symptoms.
1) Green and Red phone buttons do not work.
2) Soft buttons do not work.
3) D-Pad and wheel work intermittently.
4) (and most strange) the back-space key on the slide out keyboard does nothing, and on the virtual keyboard it flashes (to suggest that the key is being pressed) but still does nothing.
I've tried to access the bootloader, and perform a hard reset. I'm now looking for the original T-Mobile ROM to install (which was why I went into the shop), as the issue around the backspace key implies to me that the issue is in the OS not in the hardware.
Jon
Thanks already for all the input.
I've been trying all weekend in every different possible way to perform a hard reset. Fat fingering is really no possibility anymore. I've used every possible tool I had (needle-nose pliers, chopsticks, pens,...) to eliminate fat fingering.
But nothing helped. Jon (a nice guy) might have given a possibly correct diagnosis for my problem. But it wouldn't explain why I still can get into the bootloader.
Problems since receiving my phone from repairs:
Backlight changed out of itself => performed Hard Reset
Phone pad pops up and seems to start dialing => flashed new ROM
Wakes up constantly after a few seconds from standby => performed Hard Throw against the wall
As you can see, my latest problem is that the phone automatically wakes up from standby after a few seconds. The weird thing: it only does this when I put it in standby, but it doesn't wake up if it enters standby by itself.
=> NOTE: This may support the 'fat finger'-theory: the Kaiser gets some sort of keyboard input due to faulty hardware. Therefore I cannot Hard Reset my device, because of the additional faulty input.
I've used the "Clear Storage" method to perform one of my hard resets, but this has to be solved. I will be sending the phone back for yet another repair.
Thanks again for your input everyone.
Problem found?
I think I found the problem:
I just noticed that the camera button is already pushed in halfway (like when you focus the camera before you take a picture). If I push the button gently, it immediately takes a picture without focussing (it does automatically focus before taking the shot, but not on my command).
Also, when I enter the camera app, it sometimes instantly focuses. Other times I cannot focus at all.
Hard reset is still no go.
Yet another thanks for your useful help.
Maybe found the solution?
Hi Guys...
I found that by tapping the base of the phone, it "unlocks" itself, thereby making it work. It's become *S*L*O*W* as hell, and I'm really tempted to ask them to take a look at it, but right now I need all the functions, so I'm holding off.
But, give that a try and see what happens!
Jon
Thanks for still answering my question. Go community!
Dr. Strangelove said:
...
I will be sending the phone back for yet another repair.
...
Click to expand...
Click to collapse
Last week I finally received a fully functional and working Kaiser (have been waiting for that since december...). I couldn't accept a disfunctional Kaiser coming back from repairs.
The problem did indeed seem to be the camare button that was stuck. I tried really hard to get it to unblock, but I didn't work. I must say, I didn't try your method (didn't think of it).
Still thanks a lot.
I am experiencing exact same issues on my Kaiser (Tilt), it randomly starts to type stuff in the phone application on its own and I can't do anything to stop it, I have replaced ROMs, SPLs, Radios, now using a shipped rom with shipped radio but still that problem comes up after a few days of usage and doesn't go away until I hard reset, anyone knows what I can do to fix it? it's probably out of warranty. I checked the camera button and it seems fine.

[Q] Galaxy S not booting, black screen!

Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan
Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.
thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.
if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces
thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan
You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App
I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike
I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk

[Q] Phone malfunctioning majorly...

OK so in Australia we got the SGS FroYo 2.2 update in November and when I went to upgrade my phone everything went stupid. Basically I'd never needed/wanted to root or anything like that my phone was running with its basic firmware plus OCLF to fix the lag. Basically I got over excited about the update and didn't read anything and well I bricked my phone because I didn't remove OCLF. That was fine and dandy until I released that my 3br would not work anymore (don't ask my why) so i had to send it in for warranty. So thats the background/past before everything went stupid again.
Now I got my phone back and the 2.2 upgrade had been installed the repair deatils where:
- Inspected and chemically cleaned all contacts
- Upgraded handset to latest available software DTJP3
- Unit tested and passed live on air test
- Handset meets all manufacturer specifications SU
Click to expand...
Click to collapse
Now like I said I got my phone back and everything was fine & dandy but I noticed it was really slow, slower then 2.1 was. Also my D button would not work, no matter how hard i tried to press it, even when I swiped over it the blue line thing goes around it. Along with not being able to press the d button, anything located near the side of the screen would just not register my touch. Also my phone would just decide without me touching it to just select things and malfunction, type whatever text it liked, it also would constantly scroll up and down and basically just screwed my head in. Now I thought this was just a temporary error so I restored factory settings through 3BR and privacy settings method and it seemed fixed. So I applied z4root so i could OCLF back to fix the lag but that bricked my phone so I had to reset it again and then I applied voodoo lagfix (the one click method from market). I didn't really notice and difference with the voodoo lagfix so i disabled it and bam! my phone went even more stupid. So I googled and searched xda and removed voodoo entirely by flashing back to the original firmware and that seem to fix everything but the D for about 5 mins and now its not as bad as it was but its still malfunctioning all over the place and I can't even have it on the 1st screen without it constantly going into my contacts and trying to delete them or type things...
So what do I do? If I send it back for warranty will they notice that the firmwares not optus but the orginal (from samsung-firmwares.com)? will that break my warranty? Plus sending it for warranty now will mean I won't get the phone back till January at the earliest. Or can someone suggest something else to go about fixing it?
Sorry about long post, thought going into detail would be better and more helpful.
Hey mate,
If you reflash with dtjp3 from samfirmwares then that is the firmware they put on and will not be able to tell you fkd with it.
Good luck
Alex

[Q] LCD BLACK BUT STILL FUNCTIONAL BLIND, MAJOR KEYS still lit up

First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.
3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App

[Q] Touch issue

At a certain point on my screen, the phone thinks I am touching it.
I dont know how else to explain it but a 'phantom touch'.
Its repetitive and very annoying.
It seemed to start after I flashed some custom ROMS.
I flashed back to stock (2.3.5) in the hopes of it being fixed but it seemed to follow me.
Has anyone had this issue/knows how to fix it?
Thanks
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
dr. xp55 said:
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
Click to expand...
Click to collapse
It seems to have just gone away on its own. Cheers for the help anyway, would have done this if I still had the problem.
It seems to come back when I flash a ROM.
I flashed the German ICS official ROM (which is great btw), and it seems to have come back.
Hopefully, someone can provide me with a solution, perhaps its a corrupt system file?
Still, it goes away when the phone is charging.
Any ideas at all?
I'm not sure if this is helpful, but I faced the same issue when I flashed ParanoidAndroid yesterday. In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive). It was then that these phantom touches started. I set it to 100(max, least sensitive) and I couldn't get the touchscreen to register any touches at all. The Spen worked in both cases, so I just used that to reset it.
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Hi, I think this seems to be the trick.
I was unable to find the code to access the settings menu you described.
However, I installed TouchScreenTune, and that seems to be working for the moment.
Will post my results in a few hours or so.
Thanks
bloodyhippo said:
In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive)....
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Click to expand...
Click to collapse
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
novastorm17 said:
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
Click to expand...
Click to collapse
You're right, I couldn't find one that'd help either. Hmm.
Do you still have the problem?
It hasn't gone away, but I think the frequency at which it occurs has reduced
Any other ideas/any other way to do your previous method?
Cheers
Okay so here is all the information I have.
No matter which ROM I flash, the issue of the random touching continues.
Ive tried without root, and tried a complete reinstall (by formatting all data and storage)
I found a CWM restore I made 6 months ago (long before the issue started). That didnt work either.
Things that DO work:
TouchScreenTune seems to greatly reduce the frequency at which at occurs by decreasing the sensitivity of the screen, however, it makes it harder to use the phone.
Plugging in USB stops it completely, but when its removed, the issue comes back.
I thought since it is following me through different ROMs it is a hardware issue.
Does ANYONE know a fix/heard of this before?
At the moment Ive resorted to using my old IDEOS (oh god) and have begun working towards a warranty rectification.
Thanks anyone who can help
Update from Samsung:
Issue due to motherboard/touchscreen
Cheers for your help

Categories

Resources