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.
Related
Hi,
I noticed, that after a total standstill, there is now a little movement on the nike android front. I want to contribute a little share to that.
I have set up an autobuild service for the android kernel. I automatically uploads a fresh zImage with the newest patches every full hour. I also reenabled Vibration as I never had any problems with that. If there are still people aound that need a kernel without Vibration let me know, I could set up a second build, too.
[update 03.03.10] Kernel without vibration for niki100 included.
The fresh kernel is found here.
[2010.03.31]UPDATE:
- IRQ wakeups enabled -> sleepmode 1 works
- Red led flashes when sleeping
- hw3d for eclair can be chosen in commandline (not fully functional)
- Double press cam button is home on 20key nike now
[2010.04.08]UPDATE:
- Some Keypad and defconfig changes to support ubuntu
[2010.07.01]UPDATE:
- Added .patch files to downloads for all who want to compile on their own (Recommanded! Some new devs would be very welcome here)
[2010.07.02]UPDATE:
- Removed .patch files again, they don't work as intended. Just 'git apply' the "Changes compared to stock kernel" instead...
- Fixed audio (please give me some feedback if it works now)
[2010.08.30]UPDATE:
- I just was tipped of that the service has been down for full 3 months (thx youngsien)
- Service is now online again, but will from now on only be updated once a day (should be enough)
Happy Androiding everyone!
mblaster
PS: If you don't know what a zImage is or does: It is the core of the Android operating system. It is usually in the same folder like haret.exe. You can tell your Android build to use a specific zImage in default.txt
Nice idea...
That's what we need to make good android builds working on nike.
The vibration ALLWAYS freezes de touchscreen, maybe a htc p5500 model issue.
i will follow this post hourly...
OK, I included the stock kernel without vibration in the service. Have fun!
@arleybarros: I dind't mean to post here hourly, but my server will keep the kernel up to date
the stock kernel freezes after a little vibration..
shouldn't vibration be disabled on stock release?
nik2208 said:
the stock kernel freezes after a little vibration..
shouldn't vibration be disabled on stock release?
Click to expand...
Click to collapse
Yeah, you're right. The files were exchanged by my build script... Thanks for the hint, everything should be fine now.
*bump*
New updates in first post... I hope everything works
mblaster,could you post your default.txt cmdline, please? seems like nike still does not sleep, there no signs of flashing red led on mine.
my cmdline: "pm.sleep_mode=1 mddi.width=320 mddi.height=480 hw3d.version=1"
I'm running msmissions eclair.
are you running it without rootfs? there seems to be a problem with the norootfs basefiles that prevents sleeping.
yup, norootfs.
ok, got progress, I've runned android again, now nike felt asleep and flashing red led. wakeup works too - double tap on dpad center. I think that was because there was no reboot after installing after data wipe, norootfs missing some controls on power.
also, there is another power problem - MSM's standard reboot/poweroff commands from android does not working, can we fix this? device just freezing, seems like some revision on vogue's power controlls broken ours.
rzk333 said:
also, there is another power problem - MSM's standard reboot/poweroff commands from android does not working, can we fix this? device just freezing, seems like some revision on vogue's power controlls broken ours.
Click to expand...
Click to collapse
The same here with the norootfs stuff. I tried myn's donut on sqsh and norootfs. SQSH works like a charm (powermanegement, net, reboot, powerdown), but the same build/kernel combination has the problems mentioned before...
[minor UPDATE] Double press cam is home now on 20key nike
here is that someone is going to operate the headphones??
i can't use internet.
help me.
i set my carrier.but i can't use internet
[minor UPDATE] Double press cam is home now on 20key nike
Click to expand...
Click to collapse
can we make something about "Enter" key on niki100?
I've tried to run kaiser ubuntu and stuck with login - I simply cannot press enter :/
maybe some virtual button can be mapped to something?
rzk333 said:
can we make something about "Enter" key on niki100?
I've tried to run kaiser ubuntu and stuck with login - I simply cannot press enter :/
maybe some virtual button can be mapped to something?
Click to expand...
Click to collapse
Where would you like to have the enter key? I can try to fix it in, but i am not sure where to put it.
Some ideas would be:
- Put enter on cam, press WinKey once = menu, press Winkey twice = home
- Put enter un the key on the lower right (InternetExplorer in winmo?), probably better, but i dont know for shure which button it is. Dou you get a 'z' if you press it? I guess you do:
Code:
{{KEY_Z,FALSE,FALSE,FALSE,FALSE},FALSE}, // UNKNOWN KEY
Can you confirm that you get a 'z'? I will change it to enter then.
€: If ubuntu works it would be nice if you could start a thread about it. Would be great to have a full blown linux box in your pocket
Latest Kernel is working nicely on my Nike100, really impressed with the battery life now, great job on getting sleep to work. I have a request though... would it be possible to make one more kernel for the Nike 16 key? at the moment you can't type on it or use any of the keypad as the mappings are all wrong. If it would help I can tell you what keys are currently mapped to what on the 16 key. I don't know how hard it would be to change but if it is doable I would really appreciate it as it is really the last thing that is stopping the port from being day to day usable for me and other 16 key users. Unfortunately the onscreen keypad is just a bit small for typing with daily.
Thanks, hope its not too hard a fix.
MWG_Thomas said:
Latest Kernel is working nicely on my Nike100, really impressed with the battery life now, great job on getting sleep to work. I have a request though... would it be possible to make one more kernel for the Nike 16 key? at the moment you can't type on it or use any of the keypad as the mappings are all wrong. If it would help I can tell you what keys are currently mapped to what on the 16 key. I don't know how hard it would be to change but if it is doable I would really appreciate it as it is really the last thing that is stopping the port from being day to day usable for me and other 16 key users. Unfortunately the onscreen keypad is just a bit small for typing with daily.
Thanks, hope its not too hard a fix.
Click to expand...
Click to collapse
Do you have this parameter in default.txt?
Code:
board-htcnike-keypad.keypadlayout=1
If not, add it and remove other entries concerning keypad layouts (might be there from kaiser). Most of the keys should be mapped correctly. Enter key seems to be missing. Could you try to press the button on the lower right (Internet explorer or something like that, depending on the branding of your phone) and tell me if it prints the letter 'z'?
Where would you like to have the enter key?
Click to expand...
Click to collapse
iexplorer key is useless in ubuntu and android, I think, so we can remap it, camera home key is used widely in android, you dont need to open up slider to access menus
If ubuntu works it would be nice if you could start a thread about it.
Click to expand...
Click to collapse
that would be nice too, now we can run LXDE or other X windowmanager compiled for ARM, ubuntu boots up fine and works like on kaiser. you can learn how this happen for ARM in Omegamoon's blog
The patched kernels will be ready on my download page in a few minutes (compiling...). Please let me know if it worked.
Hi guys,
I finally installed Windows 7 bootcamp on my Mac, and went away on flashing kernel to XWKDD_insecure.tar, and rooting the S2 with S2 Root app. Everything went smoothly, and I now have TB Pro with a couple of apps frozen.
However, one very noticeable change after I flash and rooted was that my Applications button is very hard to activate. I thought I had imagined it, but when I unlock via Widgetlocker slider, and tap the Applications icon on the bottom right, nothing happens with the normal pressure I am used it. To activate it, I must push down with a little force for a second or two, let go, and it will go to the application folder. Also, I have also notice that when I wake the phone, the unlock widgetlocker slider is slightly unresponsive at first, I must also apply more force, hold it for a second, and slide for the slider to work. Before I rooted (6 hours ago), I can lightly tap the application icon, or light slide the unlock slider, and it would work.
Another weird thing is also buttons on the screen works fine thus far.
Anyone have this rather weird problem? I am slightly regretting rooting the phone, because the applications icon just wouldn't budge despite multiple taps... I've tried battery pulls, etc, but the problem persists, especially right after I unlock the phone.
Any input is much appreciated!
Thank you
Did you found a solution? I have the same problem, but I don't know if it's because rooting? This is really annoying.
Same here after CF-root.
and let me add that the return touch key (below the applications icon) isn't so responsive as before rooting!
I thought I was just imagining but I am "glad" you guys having the same problem.
Looking forward for a solution.
Maybe asking Chainfire ?
Well I just installed a stock rom, same thing.
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Am having the same issue with the back key and i am still stock non rooted
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
Non rooted you say, interesting...
I thought it is because I rooted it.
gil80 said:
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Click to expand...
Click to collapse
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
This is certainly not the first time I've heard about such complaints, infact a few friends also had this issue as well they had their phones replaced.
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
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.
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Having the same problem. Waiting to see others replies.
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages. Because if you put the phone in your pocket with the screen towards you body then it could be unlocking it when you get a text and the skin being close is keeping it awake. Specially if you have the glove feature turned on.
Sent from my SCH-I545 using Tapatalk 4 Beta
nativi said:
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages.
Click to expand...
Click to collapse
Good idea, but (heh) maybe I don't have enough friends but I don't get that many text messages. This happens frequently enough that I've spent a lot of time trying to figure out if some notification did something to wake up the screen, and most of the time I can find no reason for it to light up, which is why I suspect a button mash. (I also do not have the "extra sensitivity for gloved hands" option enabled.)
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Sent from my SAMSUNG-SGH-I337 using xda premium
ktetreault14 said:
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Click to expand...
Click to collapse
A reasonable suggestion. Might be the excuse I need to finally learn how to use Tasker. Wonder if I could get in a situation where I can't get my phone to wake up in a dark room, though....
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
oilfighter said:
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
Click to expand...
Click to collapse
I think this is the answer. I just got an Otterbox Defender and there's no way the buttons will get mashed in my pocket now. If the screen comes on again, I'll know there's something else causing it.
MysticCobra said:
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Click to expand...
Click to collapse
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
MysticCobra said:
Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen...
Click to expand...
Click to collapse
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
jbel25nyy said:
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
Click to expand...
Click to collapse
Great idea. That's why I posted about my Otterbox Defender in the reply right above yours.
Capp5050 said:
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
Click to expand...
Click to collapse
Good thoughts, but not exactly what I was looking for. These features might cause the screen to stay on once it awoke, but I was actually trying to prevent the screen from waking up in the first place.
I had the same thing happening to me until I put a case on the phone. I just have a hard silicone case, but the lip on the front it just enough to keep the home button from being pressed in my pocket.
I had a similar thing happening several times each day,except I would take my phone out to see that the camera was open. I figured out that it was because I had set a voice command to open the camera from the lock screen. I got rid of the command and it hasn't again
My problem is due to the intermittent wifi connection. My phone screen wakes up every time I get reconnected to the wifi network. It is so annoying.
Chris000001 said:
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
Click to expand...
Click to collapse
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Capp5050 said:
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Click to expand...
Click to collapse
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Capp5050 said:
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Click to expand...
Click to collapse
Im on a Verizon Note 3. I did as you described but it did not work. Im thinking it didnt because Root Explorer made a backup file with the non altered txt. Should I delete it to get it to work?