Hey all got two g2 both rooted running jb. They have been sitting in my drawer since December, I pulled them out yesterday to play with them and now neither one has functional soft key buttons (home, back, menu, and search) anyone else come across this issue. Also keys did work before I put them away in December, and I have tried other roms no luck. Any help would be great
Nexus 4 using xda app-developers app
As a temporary solution until you get them fixed you could add this to your build.prop:
Code:
qemu.hw.mainkeys=0
This will give you the onscreen soft keys to use (like on Nexus devices), but obviously loses you some screen space. If it doesn't work set it to =1 instead, I can't remember off the top of my head which way round it is.
It goes without saying but did you do a fresh install when you upgraded to JB?
Absolutely. And I know that there are ways around it just wondering why they broke at the same time same issue
Sent from my Nexus 4 using xda app-developers app
Related
I finally stepped into the world of evo ") I got my phone last night rooted it and installed the newest nightly from cyanogen mod 6.0. Everything is running so perfect. My only question is, is there a way to turn on the backlights at the bottom, ie. The home key, menu key etc. Thanks
E-Rock
Sent from my PC36100 using XDA App
E_Rock said:
I finally stepped into the world of evo ") I got my phone last night rooted it and installed the newest nightly from cyanogen mod 6.0. Everything is running so perfect. My only question is, is there a way to turn on the backlights at the bottom, ie. The home key, menu key etc. Thanks
E-Rock
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
These are on anytime the screen is on.
I see you are using cyanogen mod 6.0. In that case you should goto the cyanogen thread and see if other users have this issue.
actually they are only on when the screen is on and the phone is not plugged. Are they not coming on at all for you? if not were they coming on before you rooted/flashed cm6?
I have my backlight set to auto.
Anytime I take my phone someplace dark, the turn on. Even if I am not using the phone. I really like it, so I can see the buttons and know the orientation of the phone in pitch black.
Hmm, actually in looking at it now, they may just always be on. I am on hardware 02 from the google conference.
Guys/gals
I have noticed that while in CWM, the up and down presses of the volume button are acting weirdly. Sometimes it will scroll through 3-5 lines while other times it is doing what it should and moving one spot at a time. I am rooted running gummynex and using the proper CWM version. Any others experience this also?
On a side note, this sometimes disables the functionality of the 'enter' button on the right side also.
Never had any problems with CWM navigation here ... maybe re-flash CWM?
Edit: Does your volume key act weirdly just adjusting the volume? If so it may be bad hardware
Mine does the same. Its when you hold the rocker down for a long period of time. Just tap one by one and you'll be good. I kinda like the ability. It allows for faster scrolling.
Sent from my Galaxy Nexus using Tapatalk
it is only in CWM... volume functionality is perfect in normal actions. it is extremely sensitive in CWM. sometimes i can choose carefully and get it to move one option at a time, but it is far too sensitive to be fun to use in this way.
maybe i'll try the touch version and see if that is any easier. it does not seem hardware related since I have seen 3 or 4 others with the same issue only in CWM.
Be careful with the touch version. I've seen a few zip files where the developer specifically states not to use the touch version. Just a Tuesday morning fair warning.
Sent from my Galaxy Nexus using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1428338
Fix.
I've never had a problem with the touch version. I'd recommend just using that.
Sent from my GalaxyNexus using XDA App
With our beloved HTC Desire devices getting a bit aged, I expect the wear-related problems will start to increase.
I am having an issue with the BACK button (the one with the arrow on, at the bottom, second from the right) that does not respond easily. It takes numerous "convincing" keypress attempts to get it to eventually perform the action. So I guess the switch is worn out?
What would be the easiest way to rectify this problem, or is a patient wait until upgrade-time the answer?
Sent from my GT-I9300 using xda premium
Highlander11 said:
With our beloved HTC Desire devices getting a bit aged, I expect the wear-related problems will start to increase.
I am having an issue with the BACK button (the one with the arrow on, at the bottom, second from the right) that does not respond easily. It takes numerous "convincing" keypress attempts to get it to eventually perform the action. So I guess the switch is worn out?
What would be the easiest way to rectify this problem, or is a patient wait until upgrade-time the answer?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You can try a rom with on screen buttons like the one in my signature! It'll have the same buttons on screen like the galaxy nexus.
Or you could make the d-pad do the back function. System>usr>keylayout and edit the bravo-keypad. I made my search button act like the volume down button, since that one's broken.
Sent from my toaster.
abaaaabbbb63 said:
Or you could make the d-pad do the back function. System>usr>keylayout and edit the bravo-keypad. I made my search button act like the volume down button, since that one's broken.
Sent from my toaster.
Click to expand...
Click to collapse
Nice 1, worked a treat. I just made my search button volume down coz its almost completely not working and i never use search button soo now i have a perfectly working volume down button. Cheers
Sent from my HTC Desire
Highlander11 said:
With our beloved HTC Desire devices getting a bit aged, I expect the wear-related problems will start to increase.
I am having an issue with the BACK button (the one with the arrow on, at the bottom, second from the right) that does not respond easily. It takes numerous "convincing" keypress attempts to get it to eventually perform the action. So I guess the switch is worn out?
What would be the easiest way to rectify this problem, or is a patient wait until upgrade-time the answer?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It could be the ROM issue too. After changing a couple of roms, I've found that key responsiveness changes, try CM10 based builds. I'm using elk759's
Thank you so much for the suggestions so far! I'll try them out . If anyone has other suggestions, please feel free to help :thumbup:
Sent from my GT-I9300 using xda premium
Since the JSS15Q upgrade, my back button often fails to do anything. It lights up when I touch it but no action occurs. This indicates that the touch is detected by the touch screen.
I restarted in Safe Mode and the problem does not occur. This lead me to believe it is caused by an app. After restarting in normal mode, my keyboard remained Google Keyboard instead of my normal Swiftkey Tablet Keyboard. I did a short test using Google Keyboard and the back button seems to act normally. I suspect, based on this short test, that JSS15Q and Swiftkey Tablet have some sort of incompatibility. More testing is needed to confirm.
I have confirmed the conflict. Swiftkey Tablet and JSS15Q do not play well together.
Sent from my Nexus 7 using Tapatalk 4
Aha good to know.
Sent from my Nexus 7 using Tapatalk 4
jrhodes973 said:
I have confirmed the conflict. Swiftkey Tablet and JSS15Q do not play well together.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I have this problem too, but i have never has swiftkey installed.
Had that issue in the beginning but after the update have it no more well at least not that often as before it rarely fail now.
BTW have SwiftKey Tablet and I can confirm it doesn't like Android 4.3 in general. Is not the Tablet is the App.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
jrhodes973 said:
I have confirmed the conflict. Swiftkey Tablet and JSS15Q do not play well together.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Maybe it is not Swiftkey. The back button has failed without Swiftkey running but it happens rarely. Back to the hunt for the cause...
Sent from my Nexus 7 using Tapatalk 4
Back Button not responding
Same here.
I was playing either Tapped Out or Real Racing 3 one day (2 weeks ago) and all of the sudden the back button wont respond. The light goes on but it does not function.
My 2012 Nexus 7 does not have any swiftkey installed nor is it rooted.
I formatted the Nexus 7 and it is still doing the same thing prior to downloading all my apps from Google Play.
I've noticed the same thing on recently on my Nexus 7. Back button is "pressed", but fails to do anything.
Seems to occur in several different apps.
I don't have Swiftkey installed.
It's only started happening recently, but not at a specific enough time that I can directly correlate it with some specific change (or app I installed/updated).
UPDATE:
For what it's worth, I noticed one other symptom that seems to correlate with the Back button misbehaving.
I use ADW Launcher Ex, and use PIN security on my lock screen, no widgets. I have the Quick Launch disabled. Normally, there would be nothing showing in the soft buttons row. Just recently, the dotted circle of the Quick Launch showed back up. I mostly mention this because it seems something is messing with my Soft Buttons,
UPDATE 2:
I found a way to reproduce: I use Battery Monitor Widget Pro (excellent app, btw). I have recordings every 1 min, history file size 4MB. When I look at the History as a list, and swipe down through the long columns of numbers, often the Back Button fails to work. That's a pretty uncommon way to Reproduce the problem, but something I noticed.
I have also had the Back Button stop while just browsing through my files using Root Explorer.
I had this problem today and found a cure.....it works for me anyway...do not allow Google Keyboard to update to version 2.0.19133.927933a.
Version 2.0.19003.937116a works fine.
I purchased my Nexus 7 today and it booted with 4.3....had it rooted before I allowed the 4.4.2 system update to apply.
I always turn off automatic app updates when I get a new device....this helped me find the problem.
I then applied the system update and it was still working well. Had to re-root, of course.
I had made TWRP backups before and after the system update, so I was in good shape.
Next I started removing apps I did not want, then went on to update apps I was keeping.
Next thing you know...the back button stops working for most operations.
After it aggravated me enough, I restored the post-4.4.2 update backup and the back button worked fine.
I started working my way back to my goal-config and it kept working until my last step......updating the keyboard. Then it failed.
I removed the update and after a reboot the back button works fine. Did this twice to verify the fix.
Hope it helps others!
Rafael4096 said:
I had this problem today and found a cure.....it works for me anyway...do not allow Google Keyboard to update to version 2.0.19133.927933a.
Version 2.0.19003.937116a works fine.
I purchased my Nexus 7 today and it booted with 4.3....had it rooted before I allowed the 4.4.2 system update to apply.
I always turn off automatic app updates when I get a new device....this helped me find the problem.
I then applied the system update and it was still working well. Had to re-root, of course.
I had made TWRP backups before and after the system update, so I was in good shape.
Next I started removing apps I did not want, then went on to update apps I was keeping.
Next thing you know...the back button stops working for most operations.
After it aggravated me enough, I restored the post-4.4.2 update backup and the back button worked fine.
I started working my way back to my goal-config and it kept working until my last step......updating the keyboard. Then it failed.
I removed the update and after a reboot the back button works fine. Did this twice to verify the fix.
Hope it helps others!
Click to expand...
Click to collapse
I have the same issue after unlocked my N7 and did some customizations, would you please upload the working version of Google Keyboard so I could give it a try?
Thanks!
I don't currently have any online account to upload it to. If there is one here at XDA I am not aware of it.
If you PM me an email address I can certainly send the APK for the working version.
Hello everyone. I am here seeking help for my Optimus G Pro. My soft keys are not working, they just stopped working today in the afternoon. It all started when i tried to download the leaked vitnamese kitkat version for my e980. At that moment i was running G2 v5.5. The download was taking forever it had onlyva speed of 100Kb but it wasn't constant. So imagine i kept checking the progress every 10 minutes.
During one of those times i noticed the some activity on the screen as if it were being pressed in multiple places. It seemed weird to me, i just proceeded to wipe the screen. The screen acter normal again and it stood still. My susrprise was when i accidentally went into the wrong app when i was trying to check 9gag and i pressed the back button and instead it opened the app in the lower left corner. I thought it was my mistake but it wasn't when i pressed it again it highlighted a section on the running app. I stood still and analyzed the buttons and neither the back or menu button worked. I have made factory resets even a hard reset with no reaults. I am now running Sphinx v1.3 but the issue persist.
I have thought that either the phone is damaged, the keys may have been unmapped due to some issue with the old rom , the phone needs a touch firmware update or wether i have to replace the touch sensor. Though the rest of the touch screen works great. Also let me mention that the phone has not been droppen in a long time.
Maybe i could flash somehow the touchscreen firmware and it could help? I dont know.
I need advices and criteria from the experienced ones.
Anyone else has experiences this or knows whats going on?
Thank you in advance to anybody who wills to help me. ???
I had the same problem. In my case it was the screen. Lucky I am still under warranty so LG fixed that.
Sent from my LG-E980 using XDA Premium 4 mobile app
Thank you for your reply...
So, you have an idea what caused the problem? And how it coukd be fixed?
My screen on the physical end seems great.
I have had mines ever since it cameout so i doubt i qualify for warranty.
Sent from my LG-E980 using xda app-developers app
Has it been a year? If it hasn't then you should be under warranty.
Sent from my LG-E980 using XDA Premium 4 mobile app
i have same keys issue at my e980 did you solve this problem?