Related
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....
As i know that touch pro is not only can be touched on the screen but also the hard button area ( home, back, call, hang up buttons)
How can i use that feature
Which software that i need to install or how can i active it
Thank for reading my topic
What do you want exactly? Do you want to remap hardware buttons?
the hardware buttons are enabled by default. you don't have to 'activate' them.
No! My point is how can i use the sensor of hardware button ^^
Well,did you mean to use the capacitive surface of those sensors,not the buttons itself? And what exactly do you want? Please explain.
google for "G-scroll"
TomasNM said:
Well,did you mean to use the capacitive surface of those sensors,not the buttons itself? And what exactly do you want? Please explain.
Click to expand...
Click to collapse
My point is
Instead of pushing down the 4 hard buttons (call, back, home, hang off) i just need to touch it on the surface?
You can buy gscroll (mobilesrc.com), but unless you can get the 1.x series, I'd pass. The 2.x series is buggy as hell, and it seems like development has stopped. There are some free apps you can find around here as well. I'm thinking Dredscroll is one, and there was another app called Butler (I think, lol) that allowed you to use it as a launcher with gestures on the area. Gscroll lets you swipe to scroll (it's good for reading ebooks, when it's working) as well as to launch things, but it has the annoying habit of going on smoking breaks.
As I know HTC testing software,I can say,it could not be a problem to create an app of this kind,but...
- Do we have SDK for it(I didin't searched for it yet)?
- Currently I don't know,how to send keyboard hooks to the system
- I cannot prevent/disable default keyboard hooks
So that means,I am not able to solve your puzzle. Sorry.
That was my honest opinion...
I don't think he's asking about the Vibrant-Scroll Wheel, I think he's talking about the Optical Track, itself.
[As the Home, Back, Answer, & End Call buttons require you to actually PUSH them down.]
You know, the "OK/Enter" button. When you place you finger on it [NOT PRESS IT], by default, it lights up the Bottom Hardware Keys, as well as brightens the screen.
If it's not working for you, I recommend Backing up your Important Information with either SPB Backup or Microsoft MyPhone, and flashing a New ROM. There are certain Drivers that control the Optical Track. What they are, however, is beyond me.
just wanted to know what you guys and girls preferred for navigating a phones' (or a tablets') UI, and why?
what are the benefits and downsides of each?
thanks in advance for your replies!
I'm liking the capacitive so far on my Inc2, it stops dirt and grime from inserting itself next to and below hardware buttons. Also mine rotate when I turn my phone to landscape mode. If I was graced with a tablet I would like it to have as few "buttons" as possible!
I prefer hard buttons.
You don't have to look at the screen to press where you need to, and you dont need to remove your finger and reapply to click more than once.
hardware buttons
with buttons, its either you click or you dont (nothing accidental)
For navigating UI and managing things on my phone, I surely prefer the touch screen. BUT... when *anything* requires typing, real buttons beat touchscreen hands-down.
If only i could just use a mouse on my phone, lol.
Hello everyone,
I have an unlocked Nokia Lumia 710 running a custom ROM and all in all the phone is good. However, the proximity sensor doesn't seem to work properly (I don't know if the problem is from the custom ROM or from the phone itself but it doesn't really matter) - when I'm in a call I keep pressing the Hold and Mute buttons (no matter how I hold the phone) which makes me really irritated. So I was wondering, there should be registries I guess that make the buttons active when pressed during a phone call. Can someone point me to the correct registries that control if the buttons are active or not when pressed so that I will hopefully be able to completely disable these two buttons (so that when pressed nothing happens)? I don't use them anyways, so completely disabling them would certainly fix my problems. I'm posting in the general WP7 section because I guess the location of these registries would most probably be the same for all phones...
Thanks a lot in advance!
There's a registry value that is updated automatically by the proximity sensor and indicates its current status system-wide, but I doubt you'd want to use it. For one thing, it would almost certainly get immediately reset by the sensor, faulty or otherwise. For another, the Phone app isn't the only thing that uses the proximity sensor; you would end up locking out the touchscreen in some other apps too. Finally, this would also prevent you from pressing the End Call button!
I don't know of a registry value that's specific to the Phone app's use of the proximity sensor. However, even if there is, the first and third reasons above still apply.
I instead recommend that you simply tap the power button when putting the phone up to your ear to talk. This will turn off the touchscreen (and incidentally save power) and you can tap the Power button again to access the Phone app or any other app on the phone when you need them, without interfering with the call.
There may also be a tool in some built-in Manufacturer or Diagnostics app that would let you test and adjust the sensitivity of the proximity sensor. This would perhaps be the best option, but I don't know where or if it exists on a Lumia.
What I want to do is not to play with the proximity sensor itself but rather with the buttons on the screen during a call. I guess I didn't make myself clear enough, sorry about that. The idea is that when I'm in a call, the proximity sensor does not work properly and I always press either the Mute or the Hold buttons. So, these buttons can still appear during a call but when you press them, I don't want anything happening. I mean, the idea is even when the phone is not next to your ear and the screen is active during a call, pressing the buttons to do nothing. I'm just following some simple logic, which might of course be incorrect (or too simple), but I'm thinking that there is most probably a separate registry for each button that controls whether this button does some action when pressed or not. I'm also hoping that they'll be separate registries for each button so that I can, for example, disable the actions for the Hold and Mute buttons, but leave the End Call button active. The problem is that I have no idea where to look for this registry since I'm still new to WP OS.
Heck, it would even be OK for me to completely remove the buttons from the screen during a call (or substitute the current buttons with some 1x1 px transparent images), if that's possible, so if someone knows how to do even that, tell me.
I was also considering using the power button when in call but I first want to see if there is any other way to do what I want. And since I'm not using the Mute and Hold functions at all, I just thought about disabling them.
No, I understood you. I was suggesting the "fix your proximity sensor" option because normally, the problem you're experiencing just doesn't happen; that's what the prox sensor is for. Sometimes it's miscalibrated, though, or something is covering it up (some poorly-cut or installed screen protectors do this, for example).
The "Phone" app isn't a Silverlight app like third-party ones; it's a native EXE that we pretty much can't modify without using a custom ROM. That's going to make changing it the ways you suggest (disabling or resizing certain buttons, etc) quite difficult.
I'm pretty sure you don't want to disable all the buttons always, even if that were possible. For one thing, that would prevent you from hanging up, as I mentioned before. It would also prevent you from dialing any numbers, which would make the use of touch-tone automated services impossible.
The Power button option really seems like the best fit for you. It's easy, doesn't require any hacks, doesn't break any other functionality, and should be the next-best solution beyond actually solving the problem.
I see now, makes sense. In my head it sounded simpler than what it really is. I was considering resizing the buttons because I'm also using iOS and I quite enjoy digging in the OS and changing some elements, so it's possible there to, for example, substitute some buttons with transparent 1x1 px images, etc. But that's irrelevant. Looks like WP is different and I still need some time to get in to it. Anyways, thanks for your help.
P.S. The screen protector was the first thing I "accused" but unfortunately it wasn't causing the problem.
On a custom ROM, you could definitely tweak the Phone app if you wanted to. However, the way WinCE (the kernel behind WP7) works, OS files are almost always marked as "in ROM" which means that the filesystem driver will refuse to modify them while the OS is booted. This makes tempering with the stock OS difficult; we have to find ways to modify the behavior of apps and system features without modifying the apps or features themselves.
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.