Database Info

Hardware Buttons In Standby (A Serious Issue?)

I was a bit surprised to just discover, by accident, that whenever I press any of the front hardware buttons when my device is in standby then the Touch Cruise doesn't completely ignore them, it switches on the button-panel lights for a while and then they go off after the timeout. For the red hangup key it also makes a beep when the button is pressed as well as activating the button lights.
As far as I can tell this is all the device does, it doesn't switch on the screen or activate any of the functions associated with the buttons I press (as far as I can tell) but I still worry that if I accidentally get the TC in a position in my pocket (when I'm driving or just sitting down for instance) where I'm constantly activating a button then after a few hours I could either drain the battery unnecessarily by keeping the button lights permanently on and/or I could crash the device by swamping it with button-pressed messages.
Do other people see the same behaviour when their TC is in standby and is there any hack to disable this?
- Julian

Try going into Settings - System - Key Lock
and change it to the top option "Lock all buttons except power button"

Same suggestion - doesn't make a sound here
That DOES happen when he is locked and NOT in standby. Still then - the volume keys work which is not really desired but hey...

Thank you mouseymousey and SabbeRubbish. You fixed my problem, but not in the way you probably intended.
I'd just been narrow minded and assumed that, if this option was available, it would be in the Button settings app so I hadn't seen the Key Lock settings app. Thanks to you both I found this and, guess what, the top "Lock all buttons except power button" WAS set but my buttons still activated the backlight and sometimes beeped.
Confused, I changed the option to the bottom "Do not lock buttons" and it behaved as expected, i.e. any button press completely woke up the device. I then set the option back to the top "Lock all buttons except power button" and this time my problem is solved, i.e. no reaction whatsoever from pressing the front buttons.
Wierd. My TC obviously got itself into an odd state and toggling the button lock preference seems to have fixed it. I'll keep an eye on this one.
Thanks again for the invaluable advice.
- Julian

I shouldn't let misleading info lie here so here's my confession. This issue turned out to be nothing to do with my device getting confused about its key lock setting. The fact that it fixed itself when I toggled the key lock setting was a coincidence, what I did at the same time as toggling the setting was to also close down Conduits PocketPlayer which I had still minimised and running (although not playing any music) in the background.
The problem appears to be with PocketPlayer (PP) and is 100% reproducible. If PP is still running (even minimized) when the device is put into standby then I get the behaviour described in my initial post, close down PP before going into standby and everything is OK and the front buttons are totally inactive.
I have of course filed a bug with Conduits but the good news is that noone needs to worry about any generic TC/WM6 wierdness here.
- Julian

Home screen menu invisible until backlight turns off

Since updating to Frau Hottelmann's excellent bit of cooking I have an irritating issue with the menu: after using the slide-out keypad, when I slide it back in, in the home screen the (Titanium) menu is invisible until the backlight turns off. The menu when I use the keys again, it's just a nuisance having to wait for the backlight to turn off every time.
Many thanks in advance for your insights...

Try flashing again When i does not work, try another rom.

This is a regular WM6.5 bug. When your screen is off and you directly slide your phone open, the last screen will be 'forgotten'. This goes away when your screen goes back in stand-by.
The only solution is to first wake your screen (press a button) and then slide out your keyboard. Or don't use the sliding panels
Good luck!

Thanx guys
Rats! Hmmm.
Actually the screen isn't off, and it's the other way round: okay with keyboard out, menu missing when it slides back in - but maybe that's the same bug?
I'm otherwise very happy with 6.5 so I'll cross fingers that a bugfix comes along.
Funnily enough, since I posted, my Vox has started rebuilding the menu correctly again (no reboot). Let's see...

One button ONLY to wake up/unlock

Is there a program so that when your screen is locked, you can assign one button only to wake your screen and have access to the unlock slider? Now, if any of the 4 hard buttons are pressed, it brings up the unlock screen. The problem is, when the phone is in my pocket, any one of the 4 buttons, if accidentally pressed, wakes up the screen. Then of course, I hear my phone in my pocket clicking because the heat from my leg is "tapping" the screen. I just want to have the right hard button wake the phone up.
I cant find an option in the settings for this, nor any threads that discuss it.
Thanks.

I really admire you if you're able to slide the slider with the phone in your pocket.

LOL. No, I dont slide it. Just that when in my pocket, when any one of the 4 hard buttons are pressed(accidentally), i have to press the power button to lock the screen again. A pain in the butt. I what the phone to have only one hard button, not 4, that will shut off the screen when the phone is locked.

I'd like it too.
Maybe even some old school unlocking shortcut that uses hardware key combination (e.g. Home + Vol Down), rather than slide.

The Diamond, or was it the HD, had a button on the top to wake the phone up. That was nice because it was hard to accidentally press that button when it was in your pocket.

I use pocketshield for automatically unlocking my phone when the light sensor senses light coming in. An added benefit for this is that when the phone is in my pocket and I accidentally press any button, the screen will automatically shut itself off again after 10 seconds since there is no incoming light. This tool has really made my life so much easier as it gets rid of the stupid slider thing as well; you can use the lightsensor, the motion sensor and an old school sliding mechanism to unlock your phone- brilliant stuff!

Iarapilot might have meant something else indeed. Most of WM6.1-WM6.5 have a tab in the Start->Settings->Buttons screen that allows you to choose which kind of wake-up you need: waking up by pressing the Pw-ON button or waking up pressing whatever button you want. Sudden power-on is very boring, even thought you can't make your device work as you need to slide the screen. But this is a power comsuption anyway and I wonder why previous version had this chance regardless the home screen features. I do want it!!
I think it's a matter of regkeys, somebody of us who's used to "playing" with regkeys should figure out how this feature could be resumed.
Hope you help us!!

Maybe I didnt make my point very well. I just would like to have only the R hardware key, when pressed, wake up the screen so as to be able to slide to unlock. Not 4 buttons, that when any of those are pressed, wake up the screen.

I also have the problem, I only want to have only one key to wake up not other key
Please help us

Since it's free, I add myself to the request queue Having the screen wake up only on powerbutton press could be useful to reduce to 25% the probabilityof screen turning on by accident when buttons are pressed inside the pocket. Battery saver for sure.

Same here. I've been looking for this since I first got the phone! My old kaiser could do this, surely it wouldn't be too hard to implement on the HD2?

edit: nevermind, posted in the wrong thread

I don't think any software can control that as key presses send electrical signals direct to the chip/power unit, where the "power on" circuits reside. What software can do is turn it off again if not unlocked within a specific amount of time, so battery is saved. Screen touches shouldn't be an issue either if using a lock screen.

les_paulde said:
I use pocketshield for automatically unlocking my phone when the light sensor senses light coming in. An added benefit for this is that when the phone is in my pocket and I accidentally press any button, the screen will automatically shut itself off again after 10 seconds since there is no incoming light. This tool has really made my life so much easier as it gets rid of the stupid slider thing as well; you can use the lightsensor, the motion sensor and an old school sliding mechanism to unlock your phone- brilliant stuff!
Click to expand...
Click to collapse
and doesnt create any problem in normal use? u ask because if u are in call and let some other app start while talk (maybe with earphones) its quietly impossible use portrait mode because left hand always cover light sensor and screen shut down.. its the same with that app?

Did someone already found a solution? I would like such a option too. wake up only by centerbutton for instance....

[Q] Hardware buttons went crazy!

Hello!
I'm experiencing some problems with my o2 Touch Pro.
Hardware buttons on the bottom of the phone (d-pad, home, back, call, end call) are not working properly (they work fine only 20% of the time, it's random i guess).
When i press "call" button, device responds as if i pressed the "left" button. It's very annoying. The circle used to zoom in, and out around the "enter" button is problematic as well. It zooms - but but in a very chatoic way - a bit of of zoom in, then zoom out, another zoom in. Functions are just messed up.
Another time, it's all working...
How can i fix it? Is it a hardware problem?
I'm using the Energy Rom - titanium version.
Thanks for your help in advance...

Honestly, if you can't deal with it, get another device. Either that or stick with the stock ROM, less problematic (you can also keep the full function of the d-pad) but then again it may introduce other issues. Someone mentioned this being more a hardware than a software issue. Since I cannot reproduce this on my at&t Fuze, that is all I can suggest on my end.

I get some of that with my fuze; mostly, the d-pad doesn't read gestures properly. If I run compact heaps (from sk tools) periodically, it helps. Soft resetting obviously helps as well. I think it's more of a hardware issue. My problems have definitely gotten worse over time. You can also check out this tool (from an HTC test rom dump; can't remember where I got it). It's a debugger for the d-pad. At least you can see how accurately the button presses and gestures work.

Thanks.

How do the soft key lights work?

The soft key lights on this device seem to work differently then most other android devices with back light soft keys. I've been trying to figure this out for a while. When exactly does the phone decide to turn them off, and and why can't I turn them off using apps like screen filter, and even on the stock t mobile rom?
Is this a hardware or software issue?
What I know is that the soft key lights in kj6 (gingerbread) roms turn on every time you turn the screen on or touch the screen, and turn off after 3 seconds of inactivity (not touching the screen or pressing any buttons).
But it seems that in some situations the soft keys turn off and stay off, even when touching the screen, which is seemingly random. Why does it do this?
Does anybody know when exactly the soft key lights decide to turn off?

From what I can tell, the Team Acid ICS driver does what it is supposed to do -- turn on and off the lights when the magic number is written to the right sysfs location.
The control of the lights is supposed to happen in the Android world with PowerManager and LightsService. The "problem" is that it seems as though the chip that controls the touchkeys and their backlight have a mind of their own and turn on the lights when you touch them. This gets the Android world's idea of if they are on or not confused, resulting in LightsService not "turning off" the light as it thinks they are already off.
I'm working through a good way to resolve this. Messing with the framework code is not the best as it means that TeamAcid would have their own version, and keeping up with upstream changes would be more difficult. Unfortunately, how it was done in GB is something of a mystery as it isn't clear to me from the Samsung code drop.
https://github.com/teamacid/android_device_samsung_galaxys4gmtd/issues/32

Are the soft key lights on the sgs4g the same as the original us versions of the Samsung galaxy (the vibrant/captivate)? If they have a fix for this (I assume they might because they have a larger development community) , would it work for our device?

I'm looking into if I can find some dev information for the Cypress/Melfas key controller, and possibly the Atmel mXT224 and looking for other devices that use it (Motorola Atrix, for example). If I can disable the "LED on when touched" behavior, things are a lot easier.

i was wondering about this as well... my back button, is messed up and has no sensitivity at all so im trying to disable the whole bar and just use an onscreen nav bar. i know that paranoid as it in their settings but that rom eats up the battery like a mad man ill be down to zero by noon i dont get that problem with CM9 BUT CM9 doesnt have the onscreen Nav Bar
does any one know where i can find more info on adding this nav bar to CM9?

Aokp has it too

V1R3Z said:
my back button, is messed up and has no sensitivity at all
Click to expand...
Click to collapse
You might try Hefe Kernel Of Darkness (second post in that thread) to mainly turn off the touchkey backlight.
I'm curious as to what poor back-button sensitivity problems you are seeing. You can PM to keep the thread clean.