anyone know an app to get the volume rocker to wake the screen on the galaxy nexus?
"no lock" doesent work on the GN but it works on the N1 gingerbread
mush03 said:
anyone know an app to get the volume rocker to wake the screen on the galaxy nexus?
"no lock" doesent work on the GN but it works on the N1 gingerbread
Click to expand...
Click to collapse
custom roms have. such as AOKP
Yup
LTE EX Galaxy Nexus - 4.0.3 AOSP
Asus Transformer - Revolver OC/UV
volume wake
Looking for any updates on this topic
What Gnex GSM ROMs implemented this feature
i tired widgetlocker, but the feature "Easy Wake Mode/any hardware button to wake" doesn't seem to work on Galaxy Nexus unless i'm forgetting or not seeing something, seems like i went through and tried all the options of widgetlocker-but no response to volume keys when device is sleeping.
please point me into a right directions about volume wake
is there a possibility to cook a volume wake mod for other ROMs
Thank you in advance.
( Currently running stock kernel+ARHD 2.1.5 )
psak said:
Looking for any updates on this topic
What Gnex GSM ROMs implemented this feature
i tired widgetlocker, but the feature "Easy Wake Mode/any hardware button to wake" doesn't seem to work on Galaxy Nexus unless i'm forgetting or not seeing something, seems like i went through and tried all the options of widgetlocker-but no response to volume keys when device is sleeping.
please point me into a right directions about volume wake
is there a possibility to cook a volume wake mod for other ROMs
Thank you in advance.
( Currently running stock kernel+ARHD 2.1.5 )
Click to expand...
Click to collapse
AOKP has it. As has been stated already.
i'll second that.+1
psak said:
L
What Gnex GSM ROMs implemented this feature
Click to expand...
Click to collapse
Pretty much any/all AOSP based roms have implemented it (4.0.3). The only AOSP rom I can think of that currently does not have it is BAMF, but IIRC it will be in the next version.
Shortlist I can think of:
CM9
Liquid
Gummy Nex
AOKP
Many others...close your eyes, throw a dart, and chances are you'll hit a rom that has it.
I'm just curious from those of you who flashed, how is ICS implemented? There was some criticism of ICS replacing the 'menu' button and removing hardware buttons. Do the leaked rom builds use 'software' buttons also or are those functions coded to our hardware buttons (this is my assumption). Does the hardware menu button do anything (i.e. is it linked to 'menus' in apps still?)...how do you feel with the changes in 'search' button functionality in ICS?
I'm hoping to install the ROM myself soon and take a look but don't have the time now and was hoping someone could provide quick thoughts on these issues (I haven't found any reviews or discussions related to this...)
Thanks for any thoughts
brady747 said:
I'm just curious from those of you who flashed, how is ICS implemented? There was some criticism of ICS replacing the 'menu' button and removing hardware buttons. Do the leaked rom builds use 'software' buttons also or are those functions coded to our hardware buttons (this is my assumption). Does the hardware menu button do anything (i.e. is it linked to 'menus' in apps still?)...how do you feel with the changes in 'search' button functionality in ICS?
I'm hoping to install the ROM myself soon and take a look but don't have the time now and was hoping someone could provide quick thoughts on these issues (I haven't found any reviews or discussions related to this...)
Thanks for any thoughts
Click to expand...
Click to collapse
Lol why don't you flash and find out =0 jk lol no the factory buttons are still in use I believe only new ICS phones from niw on will have on screen buttons everything as far as hardware buttons work normally only thing different is screenshot is home and volume down
Yeah, i tried to pre-empt that suggestion obviously thanks for feedback, i guess im just gonna have to try it and find out what software isnt working and how search and menu are integrated into the OS and apps. Im not really thrilled with what they did with the buttons going forward actually...we'll see. thanks
I need a ics rom that has the volume button wake on it because my power button has recently got very hard to press. I am currently on the darkside 3 beta ics rom if that helps or if you could point me in the direction of an add on. Thanks!!
Wow almost 100 views and still no answer.. my my
You could always use the destruction guide below to pull the phone apart and see what's causing your power button woes...
http://www.ifixit.com/Guide/Disassembling-Samsung-Galaxy-s-2-T-mobile-T989-Phone/8179/1
That said, I imagine once official ICS rolls out of TMo corp the T989 Devs will wake back up and start cooking custom ROMs based on it. Am betting one of these ROM's will have volume wake.
...Also, you could RMA the phone... Just a though.
ronin4740 said:
You could always use the destruction guide below to pull the phone apart and see what's causing your power button woes...
http://www.ifixit.com/Guide/Disassembling-Samsung-Galaxy-s-2-T-mobile-T989-Phone/8179/1
That said, I imagine once official ICS rolls out of TMo corp the T989 Devs will wake back up and start cooking custom ROMs based on it. Am betting one of these ROM's will have volume wake.
...Also, you could RMA the phone... Just a though.
Click to expand...
Click to collapse
Very helpful. Thanks a lot
Sent from my SGH-T989 using xda premium
Someone please please PLEASE tell me if there is a way to tell the captive touchkeys to stay on when the screen backlight is on. I may be in the minority but I can't stand the lights going out while I'm using the phone. Sounds simple but I REALLY hate them going off. There wasnt an issue with the unofficial CM10 alpha 5(?). At one time I had a rom that allowed me to set a timeout in seconds OR to match the backlight. That would be perfect in my mind. It would be great if the keyboard backlights were on any time the keyboard is open (IMO). If I'm in the minority then someone please tell me where I can set it at the OS level for just me. If I can't find a solution then I will have to go back to alpha 5 and stay there.
I have googled everything I can think of. I keep getting pages about a "great" new beature of CM9 that allows you to disable the backlight altogether. Great for some maybe but not me. I bring that up to say that I have tried to find the answer on my own first.
Is your capacitive lights feature unchecked in the advanced settings? I think the majority of people who have used samsung phones don't need the lights, so that's why this feature has been implemated.
Sent from my SPH-D700 using xda app-developers app
It is unchecked. I have no problem with the ability to disable but would love to have the option to have them stay on (JB Default) when the screen is on. I don't like having to guess where the buttons are when it's dark out. It's petty I know but it really does bother me enough to not use the rom If I can't change it.
Please post questions in Q&A
Thread moved
Thanks
FNM
FWIW - I'd like to see this as an option, too. It's an annoyance, but not a show stopper. I'm actually getting pretty good at guessing where the capacitive keys actually are, but sometimes get ticked at fumbling for them.
Al
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
arschend said:
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
Click to expand...
Click to collapse
This functionality would have to be added to the CM framework. The framework is what controls the 6 second timeout and a configurable timeout setting has not been coded. Anyone is free to work that out and submit it to the CM gerrit system
Sent from my SPH-D700 using xda app-developers app
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
reiter01 said:
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
I finally got brave
bbelos said:
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
Click to expand...
Click to collapse
A year has passed. Updates have come and gone. I even switched to another phone and back to the Epic4G. Same thing bugged me as always. I took the leap and set up a virtual machine so I could compile CM 10.1. I did a test compile and came out fine. I then made the changes you mentioned (that made more sense once I got used to the built process) and it WORKED!
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Thank you so much (a year late).
reiter01 said:
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Click to expand...
Click to collapse
I've had my Epic for a week, running CM 10.1, and this bugs the snot out of me too. Any chance you could PM me a link to your build? :laugh:
Sure
I'll try to figure out where to upload it. Keep in mind I know nothing about coding for Android. It's simply CM 10.1 (newest) for EpicMTD with 2 numbers changed and then compiled. I do like that the ability to control the brightness of the buttons still works. I don't like them super bright but I do want them always on.
Download
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
reiter01 said:
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
Click to expand...
Click to collapse
Understood, and thank you good sir. :highfive:
UPDATE: Loaded, booted, and is running without a hitch. You have solved my one major gripe with CM on my Epic. Thankyouthankyouthankyouthankyou!
Glad I could help someone else. CM10.1 is so near perfect in every way, it was frustrating to have such an annoying "flaw". In the older version of CM they didn't have the ability to adjust the brightness of the buttons so I can understand some people wanting them off or fast timeout. If I ever have some spare time I will try to add this as a feature to the menu but I doubt it will ever happen.
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
reiter01 said:
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
Click to expand...
Click to collapse
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Patch
bbelos said:
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Click to expand...
Click to collapse
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
reiter01 said:
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
Click to expand...
Click to collapse
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Awesome
bbelos said:
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I installed your cm11 but havent gone through and tweaked it out. Looks like that might do the trick. I have found a couple bugs (to be expected).
1. If on a call and hit home, there is no way to get back to hang up. Have to power off.
2. While on home screen. Hitting the "menu" button at the bottom and choosing "settings" brings up the launcher3 settings. Used to be the android settings...maybe it's a change. Not a deal breaker but I prefer the old way.
Thank you for all your work. I wish there was some way I could help you out.
Ok so a run down of the problem
My Mother has recently gotten the glide as she has a mobility disorder that makes using a touch screen keyboard very difficult.
The trouble is that with the glides hardware keyboard if you long press the keys, e.g. The A key, it comes up with ASCII characters aka accents.
So what I am looking for is a way to turn off long press on the hardware keyboard or at the very least set it to a 5 second delay so as to not conflict with my my Moms typing.
I have changed the tap and hold delay in the accessibility option but this has had little to no effect.
I would rather not root or load custom ROM if it all possible
Thanks in advance of any help.
If you are using ICS+ (4.04+) Try settings>accessibility>touch and hold delay>(select your prefrence)
I don't remember if its on stock but let me know if it is as im using cm 10.2!
Edit: sorry realized that your on stock :/ this overrides everything in cm 10.2 (jb 4.3) if you change your mind about flashing let me know (you don't loose any data while flashing)
stormdude124 said:
If you are using ICS+ (4.04+) Try settings>accessibility>touch and hold delay>(select your prefrence)
I don't remember if its on stock but let me know if it is as im using cm 10.2!
Edit: sorry realized that your on stock :/ this overrides everything in cm 10.2 (jb 4.3) if you change your mind about flashing let me know (you don't loose any data while flashing)
Click to expand...
Click to collapse
I actually have already tried changing the accessibility setting to increase the delay but i think this only applies to the touch screen not the physical keyboard.
I am not against flashing a custom ROM just would like to avoid it if at all possible.