• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

menu press error simple fix.

T

tlombardi

Newbie
ever since i root my phone the menu button randomly press it self .....

well i change the time that the buttons light stay on from 1.5 to stay on at all the times....my light buttons now are on and they shout off when i lock the screen,menu button randomly press is gone like it was never even there....

well i hope i helped some one sharing my experience because is very annoying
having your phone like that ... especially when you are trying to show somebody else something in your phone .
 
tlombardi said:
ever since i root my phone the menu button randomly press it self .....

well i change the time that the buttons light stay on from 1.5 to stay on at all the times....my light buttons now are on and they shout off when i lock the screen,menu button randomly press is gone like it was never even there....

well i hope i helped some one sharing my experience because is very annoying
having your phone like that ... especially when you are trying to show somebody else something in your phone .
Click to expand...

Phantom key press has nothing to do with root.
 
I did my reserch end i know this is hardware issue.....well the only fix i could find was or ether send the phone to samsung or fix the driver.
Sorry to all if i sound like root is a bad thing no is not i root ever android devive i ever had
My samsung s2 did not had that issue
Until after i root the phone,well i went
Back to stock,factor reset the phone
And the issue was still there.
Once againg my goal was to share a fix for this issue,i been in This forum for years and been helped many times maybe it was time for me to return the favor and help some one else
 
I just reflashed my FI22 back to FG31 and then updated all the way up to FL24. I can confirm that setting touch key light duration always on does NOT fix my phantom menu keypress problem - and besides my preference is to turn those lights always OFF. However, I solved this problem a little while ago (you will find my original tutorial in the "all things root" subforum) by disabling the menu key and turning the search key into the new menu key. It's easy, and it works. I'll write up a mini-tutorial right now:




STEP 1 - ROOT PHONE:


If you are running FL24, download the "Framaroot" apk, then use this program to root your S2 using the "frodo" exploit. It works.

If you are still running FI22, download the "ExynosAbuse" apk, then use this program to root your S2 using the exynos exploit. It works. Framaroot might work too, but I don't know for sure.

If you are running a different build (such as anything Jelly Bean), your S2 is probably already rooted.




STEP 2 - BACK UP RELEVANT KEYLAYOUT FILES


If you are NOT using FL24 or FI22, I can't promise that these are the correct files for your build. Stop. Do not proceed unless you think you know exactly what you're doing.

If you ARE running one of those stock builds, then back up the following files in a root-enabled file explorer (hint: ES File Explorer has a built-in text editor, and you're going to need that for step 3):

/system/usr/keylayout/melfas-touchkey.kl

and

/system/usr/keylayout/sec_touchkey.kl




STEP 3 - MODIFY KEYLAYOUT FILES


One at a time, open each of the files listed in step 2 as text, for editing. If you are using ES File Explorer, then open the files as text with ES Note Editor. Please, now take a moment to understand what these files do (basically the phone is directed to interpret softkey presses numerically into system functions). Technically this fix will work without editing both of the files, but I like to do them both anyway. (Remember that the pound sign # in front of a line comments that line out so it isn't interpreted.) So now, replace the code in both those keylayout files with the following edits, and then save the file (make sure to leave a new blankline at the bottom of the code, as a fifth line):

Code: 
key 158   BACK
#key 139   MENU
key 102   HOME
key 217   MENU

DO NOT forget the # sign in front of the key 139 line, or your phantom keypresses will continue. By commenting out the action for key 139, pressing the original menu key (including when the phone decides to press it for you by itself) will do absolutely nothing. Also, I prefer to not allow the softkeys to wake the OS, and that is why the WAKE parameters have been edited out in my modification.




STEP 4 - REBOOT


After you save the new code to both those keylayout files, reboot your phone. From then on, the faulty menu key will be disabled, and the search key will function as your new menu key.

You may still experience a very, very minor issue where the phone hardware continues to register the phantom menu keypresses - even though this key is no longer associated with any action. You will know that this is happening because the other softkeys (home, back, and menu/search) will lock up and stop functioning temporarily, and if you use the touch key lights function they will stay on for as long as the phantom keypress is active. This is a much, much better problem to have than the original phantom keypress issue! If your softkeys do lock up you can either wait it out, or turn the screen off and immediately on again (this always works), or sometimes you can kick the other softkeys back on by simply pressing the original menu key (the one which you disabled using this tutorial).




Please, I'd love to hear your feedback!!! This fix works!
 
You must log in or register to reply here.
Back
Top Bottom