My soft keys died on my Rezound for no apparent reason. They intermittently work but it is very painful.
I worked on this for quite some time and I tried many mods on various forums. I wanted to post up this simple fix that works on Rezound with cyanogenmod 10.1.
Download "Build Prop Editor by JRummy Apps Inc." or similar off of the android market. Add entry "qemu.hw.mainkeys=0" to build.prop. Reboot and you should see on screen soft keys.
Now download "Capacitive Button Brightness" by Sleepy Dragon and turn off the hardware key light:
Again, I didn't come up with all of this, but I am putting it in one place to help others with failing hardware.
benjordan06 said:
My soft keys died on my Rezound for no apparent reason. They intermittently work but it is very painful.
I worked on this for quite some time and I tried many mods on various forums. I wanted to post up this simple fix that works on Rezound with cyanogenmod 10.1.
Download "Build Prop Editor by JRummy Apps Inc." or similar off of the android market. Add entry "qemu.hw.mainkeys=0" to build.prop. Reboot and you should see on screen soft keys.
Now download "Capacitive Button Brightness" by Sleepy Dragon and turn off the hardware key light:
Again, I didn't come up with all of this, but I am putting it in one place to help others with failing hardware.
Click to expand...
Click to collapse
Want a better trick? Grab the latest cm10.1 build and enable the PIE settings. You can disable the NAV keys so they don't take up space.
Related
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
aaron580 said:
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
Click to expand...
Click to collapse
Do a search for a utility called Advanced Config, it has a setting to change the backlight timeout, among a lot of other things. You'll need to have the ARM4i version of ppc .NET 3.5 installed also.
BEWARE: Use the tool at your own risk. Don't turn menu animations and start menu animations on, as it has caused my start menu to go really wonky (all the colors are jumbled and its impossible to read) Turning this off made it behave as expected. Just a warning
Hey thanks man. I didnt even know that setting was in advanced config and ive used since the mogul lol.
Doesnt work
I have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
oldquser said:
i have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
Click to expand...
Click to collapse
it can not be changed
This is one of the most annoying things about the TP. Anytime you pause for 5 seconds the keyboard backlight goes off! Grrr!
No kidding. I completely disabled the light sensor on my P4000, it was always on as long as the slider was open. I even watched an hour long episode of top gear while I sat in a Mazda dealership while having an oilchange done on my car.
I too have been equally frustrated with this. With no solution in sight, I think I might have thought of a program that could save our sanity. The only problem is that i've only THOUGHT of it and it doesn't exist yet. I've started a thread in the 'Development and Hacking' section. Here's the link http://forum.xda-developers.com/showthread.php?t=490267
Add comments, add ideas, just add support
Both the on-screen keyboard and the menu keep annoyingly popping up on my Viewpad7. It is driving me crazy.
At some point I thought it had to do with how I moved the device around, but I still think it's a random thing. It was/is a problem before and after loading it with a custom rom.
Is this a known hardware (or software?) bug ? If so, is there a cure for this? I have looked for settings, but was unable to find them. Thank.
SWVer=3.16K
MODEL=FM6-0001
HWVer:103
Android 2.2.2
Hi
Have the same problem and some other users here too.
Seems the Touchscreen/Softkeys are faulty and have to be replaced.
I bought mine 1 week ago and day by day it went worser. I didn't upload a custom rom so far, so it's a stock problem.
Now every 2nd time I take the device it vibrates and menu/keyboard keeps popping up/down. Looks like, the "menu" softkey does his own business, right?
Also the G-Sensor/Compass seems to be defective for me - after a few hours I have to calibrate always.
I made some videos, look at this thread:
http://forum.xda-developers.com/showthread.php?t=1258052
Where have you bought yours?
Regards
With my device it was when I held it in landscape mode and touched the bottom part of the right side or the rightmost part of the bottom of the device itself. It was also HWVer 103. You will most likely have to get the screen and soft keys replaced like I did.
Sent from my ViewPad7 using XDA App
Or, it could be just be a "normal" thing with Froyo OS itself, I've noticed it on 2 newer build - both ITE enabled - in U.S. market.
SWVer=3.41
MODEL=FM6-0001
HWVer:107
Android 2.2.2
This happened only on certain Apps - even when Auto Rotation under Settings are turned off, it will switch to the "opposing" mode and won't go back once it make that orientation change, i.e. YouTube whereas Angry Birds will stay landscape all the time. Device has been calibrated & sensors working, as I had no issues with GPS status & Maps, etc.
Should be a simple fix or patch on the OS or custom ROM .... BTW, I'm running the stock, rooted 2.2.2 ROM while waiting for an OC one with the ITE kernel working to boost the Quadrant scores, LOL.
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
astuermer said:
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
Click to expand...
Click to collapse
Hmmm, interesting after I checked out a few YouTube videos & it sounded like it's all HWVer 103 yet running Froyo 2.2.2. Is the device ITE enabled as I noticed that the pop-up keyboard is "standard" whereas mine has Swype style keybaord with ITE.
It's a pain to get it returned, exchanged & repaired at the authorized factory service center and be without the use for 2+ weeks, unless one's within a 30 days period & can send it back to the place of purchase for a new one (could take just as long)
Another post mentioned a new stock ROM just being released, it might be worth an effort or try to flash it (FM6-3350-0-1008-A01.nb0) upon downloading & using the SUTL3 app to do it - would need to root it again - if one is brave enough (since it's going back for repair/exchange anyway?)
BUT, I'm guessing whether this newly released stock ROM is for ITE devices vs. non-ITE ones with HWVer 103, 106 and 107's ???
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Brought it back to the store for repair. I think they put a new screen and cover (back) on it. Works like a charm.
flez1966 said:
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Click to expand...
Click to collapse
Can you describe more precisely how and what did you do or can you (better) do some photos?
Did you pulled off a back cover and inserted a piece of paper somewhere?
Need to experiment
Software solution
This is a solution from a user 'retrochip' from 4pda.ru forum
(Link to original post in Russian and i'm not able to post is here)
1. Root your device (can be done with Gingerbreak)
2. Find out codes for Menu button and Search button (229 and 217)
3. Edit configuration file /system/usr/keylayout/qwerty.kl (you can use RootExplorer)
In qwerty.kl:
Find text:
key 217 SEARCH WAKE_DROPPED
and change to:
key 217 MENU WAKE_DROPPED
Find text:
key 229 MENU WAKE_DROPPED
and change to (just comment it with #):
#key 229 MENU WAKE_DROPPED
Save and reboot.
Now Menu button isn't active and Search button works as a Menu button.
No annoying random popping keyboard anymore.
This has killed my all soft buttons, now the only option is to fix it in adb, because screen keyboard doesn't appear in terminal, I need to touch menu then screen keyboard.
Is there any mod that can disable notification LED and sensitive buttons LEDs forever? I know there is a few apps that can do that. But I don't wanna use apps, I noticed some custom ROMs ship with that option. I'm using stock ROM. Sorry for creating a new thread for that. But I can't find a solution for EVO 3D that would work for me. Thanks
I'm sure there will be something released like that. Nothing to my knowledge as of yet. Just something to dim the capacitive buttons.
And this goes in the Q&A section. I hope you have thick skin. Pm a mod to have it moved
Sent from the CM powered 3d
It wouldn't be too hard to do. You can see what needs changed in the kernel in my thread here. I have a version that has no capacitive LEDs and the notification LED will shut off after 5 mins or so.
plotnick said:
Is there any mod that can disable notification LED and sensitive buttons LEDs forever? I know there is a few apps that can do that. But I don't wanna use apps, I noticed some custom ROMs ship with that option. I'm using stock ROM. Sorry for creating a new thread for that. But I can't find a solution for EVO 3D that would work for me. Thanks
Click to expand...
Click to collapse
well... not sure about the blinking LED's... but let me ask you this: how will you know when your phone is charged?
and as for the soft keys, if you have root explorer, navigate to...
/sys/devices/platform/leds-pm8058/leds/button backlight/currents
when you select the button backlight directory, the "currents" is a file. long press on this file until a little menu pops up, select "open in text editor" the value there should be default 20. change it to zero, then hit your menu soft key and select "save and exit"
your leds are now off.
EDIT** and before you do all of that, you will need to select the little grey box at the top of root explorer to mount the system files as "RW", otherwise you wont be able to edit the currents file (as it will be read only)
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
it worked but only until the next restart. It restores default value everytime... Why?
plotnick said:
it worked but only until the next restart. It restores default value everytime... Why?
Click to expand...
Click to collapse
because the LED is controlled by the kernel... so, although you can manually fix it for a moment to the value you want, every time the phone boots, the phone resets the value.
the only way to make it permanent is to have a kernel with disabled LEDs
plotnick said:
it worked but only until the next restart. It restores default value everytime... Why?
Click to expand...
Click to collapse
If you just don't want the bottom buttons to light up, use the kernel I linked in my earlier post (assuming you are using a 2.3.4 ROM). If you're still using a 2.3.3 ROM, you can find a kernel call nolights made by joe85 (which is where I found the changes to make in the kernel for 2.3.4).
Yay! Now i will finally be able to sleep at night!
Bear with me here, this issue is kind of hard to describe. When I am playing a game that requires touch inputs from both hands, I often get bugs. It's most obvious in games that have controller-style overlays. As is normal, I am using my left thumb to tell a character to move right or left, and then I press the button on the right to jump. However, when I release my jump, I stop running. The screen no longer recognizes that my left thumb has been pressed down the whole time and should still be moving in the direction I am pressing. This happens in Bean's Quest, Chono'n'Cash, Delver, Gunman Clive, and any other game of this nature I have tried on my device.
I played some of these games just fine on my old Evo. Is anyone experiencing this issue? I experienced it on stock as well as several custom roms I have tried.
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
gutrrob said:
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
Click to expand...
Click to collapse
Doesn't seem to have fixed my issue, I am still having problems with some two finger games. I will be using two fingers just fine, when I remove one finger from the display the first finger is no longer recognized even though it is still touching. I have to remove the first finger and press it again every time.
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
ryanalan82 said:
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
Click to expand...
Click to collapse
Appears that widgetlocker is the culprit! Is this issue documented or known, exactly? What causes it? Thanks so much for the help. I will surely miss widgetlocker.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I encountered this recently
It seemed to get "stuck" after using multi touch gestures in-game. Tapping the game with two fingers often "unstuck" it, but overall it was extremely frustrating.
This was on an APK not designed for the phone, though
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Racer Of All said:
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Click to expand...
Click to collapse
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
ryanalan82 said:
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
Click to expand...
Click to collapse
Did you try my edit 2? The Retain System keyguard? I can assure you that I have Widgetlocker installed and I have the 10 inputs (that video was recorded with widgetlocker running).
[SOLVED!] - HTC Evo 4G LTE touch screen trouble - WidgetLocker is the problem
Retaining system keyguard in WidgetLocker worked for me! Thank you for this Racer for All. (Actually I found your YouTube video, and a link to this thread)
I was wondering why all the games I played all of a sudden stopped functioning properly (in terms of touch controls... Example: MineCraft PE, moving forward and trying to look left or right - suddenly character would stop moving.)
Sorry to dig up an old thread, but I want people to know if they have WidgetLocker (and don't want to uninstall it) just go to Settings - Advanced - Retain system keyguard - zmag
Hi all, I am wondering if anyone knows how I can disable the touch capacitive buttons on the flyer/view.
I use my tablet in landscape a lot, and end up using the bezel as a handle and then hit the buttons, I am running DextersJB14 rom with the patch.
Any help would be appreciated.
Hm, strange enough, at the moment I use DextersJB16 and these buttons are not active. I used 14, 13 and 12 and cannot even remember the buttons were active... Did you look through dev settings?
i believe he is running mobileUI edition and i activated buttons here, and a fault in the wifi build.prop also enables the softnav buttons.
if the build.prop is modified , the hardware buttons remain active (as many requested for mobileUI) and softbuttons goes away.
it will be fixed so softbuttons are gone in next update, hardware buttons remain active in mobileUI
PabloFiasko said:
Hm, strange enough, at the moment I use DextersJB16 and these buttons are not active. I used 14, 13 and 12 and cannot even remember the buttons were active... Did you look through dev settings?
Click to expand...
Click to collapse
Interestingly enough, the buttons are not lit, but do respond. I didn't see any settings that appeared to be able to change this. Might be nice to make this a toggle setting in the future, though I don't know what that would entail for Dexter. I suppose I could try out 16, didn't realize it was out.