Database Info

[REQ] "Volume Keys as Take Picture Key" in camera application

hi
is there any application or configuration to map the volume keys -one of them or both- as the camera shutter key for taking pictures?
as I can see, the AE buttons program does not do that.
thanks

I totally second that.
What a pity that there is no physical button to take picture.
Everybody knows that touching the screen will induce vibrations and blurry pictures.
If anyone could realize this it would be awesome.

I agree,
It would have to only take pictures when the camera is on tho, dont want to use up a button all the time, there just arent enough of them!

+1 also would like to have something like this

goog idea, count me in on this

+1 it was only a matter of time till this thread would appear

Volume keys CAMERA
Hi, with AEBplus you can easy do this.
Go AEBplusSettings=>Volume Down and set: 1: Volume Down 2: "Anything you wish" Long:"Camera"
OK
Now camera will start with the long press of the Volume Down key
vaskodogamagmail said:
hi
is there any application or configuration to map the volume keys -one of them or both- as the camera shutter key for taking pictures?
as I can see, the AE buttons program does not do that.
thanks
Click to expand...
Click to collapse

ilyachelsea said:
Hi, with AEBplus you can easy do this.
Go AEBplusSettings=>Volume Down and set: 1: Volume Down 2: "Anything you wish" Long:"Camera"
OK
Now camera will start with the long press of the Volume Down key
Click to expand...
Click to collapse
you missed the issue.. we would like to take pictures with a button, not start the camera itself..

thanks
it is great that some people here liked my idea I am impressed.
so if anyone here can make a mapping program for the camera application to take a picture when one or one of the volume keys are pressed to take a picture would be GREAT. because it is the most lacking option that HD2 has.
Thanks again everyone.

I guess it will be difficult...
But I'm sure someone can develop it. There are many talented people here at xda .

I think Green button will be better because if you to take a photo he is "friendly finger".

G-ThGraf said:
I think Green button will be better because if you to take a photo he is "friendly finger".
Click to expand...
Click to collapse
true..... +1

you know, every button that is more finger friendly.
I am not insisting on volume buttons.

lol http://forum.xda-developers.com/showthread.php?t=644318

found
found this:
http://www.scilor.com/leocameraanykey.html
try it

hukpin said:
found this:
http://www.scilor.com/leocameraanykey.html
try it
Click to expand...
Click to collapse
Been using this for ages, works perfectly. Make sure you download the latest version from Scilor's website - it let's you press and hold any key to zoom in, then short press any key to take the picture - pure genius!

i tried this but it doesnt work at all for me i am using Energy rom with 2.07.50 radio help please?

AE Button Plus for some reason wont make any of the keys that i have tried to change to take a picture, i bought it in hopes that it would work but i have had no luck, so i just wanted to tell ppl so they dont waste there money, its a nice program and im sure it works just fine but just not for what i need it to do. it could also be that i am on NRG rom and that may be the problem because a while back i was able to use the KB config app to change the vol up key to take a picture and it used to work just perfect, but i think NRGZ28 changed something a while back and it wont work anymore on any of his roms. unless i am doing something wrong, but the same settings that worked before wont work any more. lol that just my 2 cents!!

http://www.scilor.com/leocameraanykey.html - this worked perfectly.. thanx!

Scilor's Leo Cam Any Key app
ignore my poist

Dead Space works on Evo4G

I posted this in the Evo3D forum (since I upgraded to the 3D) but I do still have my OG 4G and recently installed DeadSpace, which is "exclusive" to the xperia Okay right now... But if you look you can find it
Well, it works on the original 4G as well! And plays pretty well I might add? I was surprised.
One little caveat with the game is the lack of a dedicated "lower weapon". But that can be worked around by simply bringing up the in game menu and exiting it. It lowers the weapon. But if you want a dedicated button. You can do this.
OK. This isn't a mod of the actual game... I'll (pretend i know what I'm doing and) look into it though.
This is an edit of the phones actual keylayout file in order to trick the game into thinking we have an L1 button to.make lowering the weapon much easier.
First. Make a backup...for me? And you... Help me help you and just do it.
Either adb pull /system/user/keylayout/supersonic-keypad.kl
Or
Use root explorer and just text edit that file. We want to change key 115 from VOLUME_UP to BUTTON_L1
Remember to back up!! Save the file and reboot.
If you did an adb pull. You'll need to remember to adb push the file you just edited.
"Adb push supersonic-keypad.kl /system/user/keylayout/"
After the restart. Load up dead space and Viola! Easy weapon lowering!! If you want the function of that key back, restore your backup and reboot.
A problem with this method is you lose the ability to actually up volume..unless you change the file back and reboot again :/
Sent from my PG86100 using Tapatalk
Sent from my PG86100 using Tapatalk

This is awesome! However, I do like keeping my Volume Up functionality :-/ is there a way to do this for my Home button or something? And does functionality return to normal for these buttons once the game is exited? I'm playing on a Samsung Galaxy S2. I'd much prefer to do this with the Home button since it's a hard physical button on the SGS2 rather than a soft key. I think everyone can agree we'd rather a modded version of the game where we have a method of lowering our weapon easily, heh.
Also, instead of pulling up the menu and exiting to lower weapon, I find that double-tapping on yourself to do the quick 180 turn is more convenient for lowering without a button mod.

rkaplan2 said:
This is awesome! However, I do like keeping my Volume Up functionality :-/ is there a way to do this for my Home button or something? And does functionality return to normal for these buttons once the game is exited? I'm playing on a Samsung Galaxy S2. I'd much prefer to do this with the Home button since it's a hard physical button on the SGS2 rather than a soft key. I think everyone can agree we'd rather a modded version of the game where we have a method of lowering our weapon easily, heh.
Also, instead of pulling up the menu and exiting to lower weapon, I find that double-tapping on yourself to do the quick 180 turn is more convenient for lowering without a button mod.
Click to expand...
Click to collapse
Or bringing up your Nav Point Guide. Any of those work. And no, after exiting the game the functionality of the button doesn't come back. The only way to get it back is to reedit the file and reboot the phone. I have an Evo3D and have set the lower weapon button to "Focus" on the camera button. I don't lose the function of the actual camera button. Just the first click which is to focus the camera. I don't mind at all because I can still tap on the screen to focus in on something.
Since the GSII has physical buttons you might be able to change one of those. You should be able to change any hardware button except power of course. This mod really isn't as convenient if the phone doesnt have a camera button or some other button that isn't used hardly at all. Lol
Sent from my PG86100 using Tapatalk

@OP.
Nice walkthrough and thanks for sharing. I doubt I'll personally use this, but still, thanks for sharing and good walkthrough/instructions.
Sent from my PC36100 using xda premium

this is awesome...my only issue is i am having a really hard time finding the apk...
any hint ..

i also cannot find the game any where. im willing to buy it, just cant find it.

[DEV] Getting Headphone Vol+/Vol- working on Android

Hi there,
as I mentioned in different threads, I noticed, that it is not possible to change the volume of your device via headphones (in my case Beats Tour with ControlTalk). I did some research about it and found, that Apple has got a patent on this procedure, so it is not possible to implement this in Android devices.
As is did some further research I found the basics, how it is working. As far as I understood the volume control is possible because of different resistors (three) in the cable. Each of this resistor is bound to one button (vol+/play-pause/vol-). If you press one button, the amperage is reduced because of the resistor. Now the only thing that has to be done is to interpret this amperage and decide which button was pressed. I was wondering why exactly the Android devices are not able to recognize the clicks on vol+/-. I did some research and testing again and found out, that "Headset Droid" does not even recognize, that the button were pressed, "Headset monitor" does not show any event. The funny thing is, that, if I press vol+ and vol- together, the click IS recognized, but the device interprets it as a click on the play-pause button. With this I would say, it is not a
hardware issue, it should be software, kernel, related.
I looked into the latest XE kernel (pyramidLE-crc-2.6.35) and searched for different keywords, but can’t find the exact files, where the headset control is configured (there must be any files, cause htc headphones are working like a charm with previous/play-pause/next). I've got two ideas how this could work.
Add some code to recognize the button-presses and interpret them correctly. That would be the elegant, clean way.
Another idea is, that we could get every headphone treated like htc headphones (vol+ would be next track, vol- last track). There is an app to change the htc previous/next buttons to work like vol+/- so that would be enough. That would be the "easy" way, but more dirty.
Some more information: I did not change anything in the kernel and never compiled the kernel, so I can’t say, if I'm on the right track.
Here is what I found in the kernelfiles so far:
\arch\arm\mach-msm //it seems, that there are some amperages are configured here, but it does not seem to be the right ones...
Code:
/* HTC OTHC Driver - BEGIN */
[...]
static struct hsed_bias_config htc_headset_othc_bias_config = {
.othc_headset = OTHC_HEADSET_NO,
.othc_lowcurr_thresh_uA = 100,
.othc_highcurr_thresh_uA = 500,
.othc_hyst_prediv_us = 3000,
.othc_period_clkdiv_us = 3000,
.othc_hyst_clk_us = 45000,
.othc_period_clk_us = 6000,
.othc_wakeup = 1,
};
[...]
\arch\arm\mach-msm\htc_headset_mgr.c //here’s the headsetmanager, the type of headphone seems to be set here
Code:
[...]
switch (hi->hs_35mm_type) {
case HEADSET_UNPLUG:
state = "headset_unplug";
break;
case HEADSET_NO_MIC:
state = "headset_no_mic";
break;
case HEADSET_MIC:
state = "headset_mic";
break;
case HEADSET_METRICO:
state = "headset_metrico";
break;
case HEADSET_UNKNOWN_MIC:
state = "headset_unknown_mic";
break;
case HEADSET_TV_OUT:
state = "headset_tv_out";
break;
case HEADSET_UNSTABLE:
state = "headset_unstable";
break;
case HEADSET_BEATS:
state = "headset_beats";
break;
case HEADSET_BEATS_SOLO:
state = "headset_beats_solo";
break;
case HEADSET_INDICATOR:
state = "headset_indicator";
break;
default:
state = "error_state";
}
[...]
As I never worked in kernel before (I am experienced in C) I don’t know whether I'm doing it wrong or not. Some help and any suggestions would be helpful, perhaps we can get this working.
I hope you understand my thoughts and problems, it's hard to express them in german and it's even harder in englisch
Kind regards,

I have also wanted my tour headphones volumes buttons to work. Thanks for this hopefully a solution could be near.

Dev of Headset Droid here.
I'd say it's a cool initiative to try to make the volume buttons work. The last time I researched the issue, it seemed to be a hardware problem at the 3.5mm plug. My guess for why clicking both vol+ and vol- generates a play/pause, is that by pressing them both, the play/pause button might actually be pressed. Of course, I could be wrong about this.
Either way, to give you an idea of what to aim for: Catching the volume button clicks globally is a lot harder than to catch the next and previous buttons in Android. Headset Droid doesn't support vol+ or vol- presses, but will only show play/pause, next and previous in the headset monitor.
If you somehow manage to get the volume buttons working as they should, the volume level should change as if you pressed the volume buttons on your device.

Headset button controller app works fine with beats. My set up is long press to change track on either button and short press to increase/decrease volume
Sent from my HTC Sensation XE with Beats Audio

tvkanters said:
Dev of Headset Droid here.
I'd say it's a cool initiative to try to make the volume buttons work. The last time I researched the issue, it seemed to be a hardware problem at the 3.5mm plug. My guess for why clicking both vol+ and vol- generates a play/pause, is that by pressing them both, the play/pause button might actually be pressed. Of course, I could be wrong about this.
Either way, to give you an idea of what to aim for: Catching the volume button clicks globally is a lot harder than to catch the next and previous buttons in Android. Headset Droid doesn't support vol+ or vol- presses, but will only show play/pause, next and previous in the headset monitor.
If you somehow manage to get the volume buttons working as they should, the volume level should change as if you pressed the volume buttons on your device.
Click to expand...
Click to collapse
nice to have you here!
i thought the same about pressing vol+ and - at the same time, bit i took a close look, the button itself (i mean the part of the button that you are actually seeing) is not moving while pressing both.
whats the difference between the htc buttons (next/previous) and, lets call them, "apple" ones (vol+/-). I read about how 3.5mm plugs are technically working and I cant imagine, that htc headphones are working THAT different from "apples" version. I had a nice article about that, I will search for it and post it here.
//EDIT: Can't find it anywhere... read the first post, I tried to explain it, hope you understand how it works.

Just some small information (sorry for double-post): Found this - reverse engineering apple headphones - and this today - reverese engineering htc headphones. It seems that it is indeed a voltage drop, that lets the system recognize the button-presses in BOTH headphones. I'll have a closer look in the evening when I'm home from work and will compare the results, if it’s similar, we might get it working by a software patch.

The second link is broken for me, but if the plug plays no role in it as you suggest, it does sound a lot more promising. : )
I'm still not convinced about pressing the two volume buttons not trigging the play/pause button, though. I've got some earphones with 'Apple' volume buttons as well (a-JAYS Four) and I can't reproduce what you're describing on my Nexus One running CM7.1.
I'll be looking forward to hearing what you find out later on. : )

Again some news and could be, that I need some help...
As far as I can see, the current cycle in both headphones (apple and htc) are exactly the same, except for the different resistors, which would explain the different voltages.
Regarding code I'm stuck at this function in \arch\arm\mach-msm\htc_headset_mgr.c
Code:
static void button_35mm_work_func(struct work_struct *work)
{
int key;
struct button_work *works;
wake_lock_timeout(&hi->hs_wake_lock, HS_WAKE_LOCK_TIMEOUT);
HS_DBG();
[B]
works = container_of(work, struct button_work, key_work.work);
hi->key_level_flag = works->key_code;[/B]
if (hi->key_level_flag) {
switch (hi->key_level_flag) {
case 1:
key = HS_MGR_KEYCODE_MEDIA;
break;
case 2:
key = HS_MGR_KEYCODE_BACKWARD;
break;
case 3:
key = HS_MGR_KEYCODE_FORWARD;
break;
default:
HS_LOG("3.5mm RC: WRONG Button Pressed");
kfree(works);
return;
}
headset_button_event(1, key);
} else { /* key release */
if (atomic_read(&hi->btn_state))
headset_button_event(0, atomic_read(&hi->btn_state));
else
HS_LOG("3.5mm RC: WRONG Button Release");
}
kfree(works);
}
I tried to roll back the events that are triggered by a keypress and the different functions are (from the first to the last):
??-->button_35mm_work_func-->headset_button_event-->button_pressed-->??
But I does not understand how button_35mm_work_func "does know" which button has been pressed... I'm stuck there for the moment :x
I do not want to know whats coming after button_pressed, cause I think its enough to get the button working as next/previous for the moment. Then we can look into volume control.
If any kernel-dev would be helping it should be easier, as I said, I never worked with kernels before, still learning.
So far.

loliman,
I just found this thread .. how is it coming? Any slightest light here? like at least a punch in volt signal and all?

Forget to tell you... I'm at vacation till tomorrow (friday). I found some more things and compiled a Kernel with some changes. I'll tell you when I'm back home.
Sent from my HTC Sensation XE with Beats Audio using XDA App

loliman said:
Forget to tell you... I'm at vacation till tomorrow (friday). I found some more things and compiled a Kernel with some changes. I'll tell you when I'm back home.
Sent from my HTC Sensation XE with Beats Audio using XDA App
Click to expand...
Click to collapse
Oh my ... you have fun now .. but yeah .. keep us posted!

jeebsion said:
Oh my ... you have fun now .. but yeah .. keep us posted!
Click to expand...
Click to collapse
loliman said:
Forget to tell you... I'm at vacation till tomorrow (friday). I found some more things and compiled a Kernel with some changes. I'll tell you when I'm back home.
Sent from my HTC Sensation XE with Beats Audio using XDA App
Click to expand...
Click to collapse
no news yet, huh? :-(

Some bad news... I tried some things yesterday wich didnt worked and now I accidently deleted my virtual machine (linux...) I'll creat a new one and try some more things (I've got some more ideas) tomorrow, I'll post more recently in the next days, sorry, had been busy

Any luck on this?

Any news? I'd love to help, though I've got no experience with C or kernel level code. How are you reading the headphone amperage? What about just writing a headphone button driver from scratch? I was just thinking simply detect an amperage change and pass that info up to handle everything else in the Android framework, but I'm not sure exactly how to do that . How have you gone about this, and if I were to experiment, where should I start?

Its been a while but I am wondering if any things changed with regards to this. I got a Klipsch S4i as a gift and I know it wont work on my Droid X2, hate to give away these headphones they sound so sweet.

I was hoping for a fix so I can use the volume control on my Sennheisers, but then my gf's cat chewed through them so now I can be patient
Sent from my Nexus 4 using Tapatalk 2

Beats volume boton
loliman said:
Some bad news... I tried some things yesterday wich didnt worked and now I accidently deleted my virtual machine (linux...) I'll creat a new one and try some more things (I've got some more ideas) tomorrow, I'll post more recently in the next days, sorry, had been busy
Click to expand...
Click to collapse
loliman, what happen with this research? did you finf something more? or did you just quit ? im asking because im trying to do the same....

I have ludacris
Hey anything new found i found this problem with my sould by ludacris sl49 i bought them for 80 euro and they didn't even post a sticker on the goddamn box or somewhere visible they ts all should just make universal drivers for earbuds and headphones this anoyes me only the middle button works for play and pause stupid bull****

From what I've seen it appears to be a patent issue with apple being the bad guys. I may be wrong though.

Power Button on HTC OneX

Does anyone know of an existing mod or another way to wake my phone? I would prefer to wake the phone with the volume toggles instead of the power button at the top. ::Small hands::
Any help would be greatly appreciated. Thanks.

wake up "call"
I had wondered about the same thing when i got my one x last week. I find it really inconvenient to wake up the phone using the top button. It seems like you have to put a lot of pressure on it just to actuate it, plus it sits at a weird angle that makes it quite awkward to press. The other concern is the weird placement of the hdmi charger port on the side of the phone instead of the bottom.
Lastly, I find the volume rocker on the right side of the phone placed too close to the center instead of closer to the top (making it easy to press accidentally) and they are much too sensitive. I've lost count of the number of times I've inadvertently increased the volume to the detriment of my ear drums. I did, however, get a Speck case that alleviates that problem, BUT, exacerbates the issue with the power button that is the subject of this thread. its just too hard to actuate the top button with the case on, never mind trying to to take a screenshot using it and the capacitive home button. REALLY awkward...
I've just crossed over from IOS to android so for now I only know iphone. There was an app available from Cydia (app store for jailbroken iphones) that allowed me to assign the iphone buttons to just about anything. I had hoped there was something like this app in Play store but I'm still new to android so I'm having to rely on the members who have been at this for a while.

Well I just found an app in the play store called JustFlip only played with it a little but seems to work on the one x does not use volume but by flipping the phone you can turn it on and off and set how many flips and how fast for it to activate has debug feature but it worked on the first try with default settings have not tested when phone is off for an extended period of time but looks like it has potential will test more and it does not require root
Edit
After playing some more it seems it does not always work and when it does it opens to the app not my home screen. Kinda annoying well it was worth a shot.
Sent from My Nocturnalized Beast

E.Cadro said:
Well I just found an app in the play store called JustFlip only played with it a little but seems to work on the one x does not use volume but by flipping the phone you can turn it on and off and set how many flips and how fast for it to activate has debug feature but it worked on the first try with default settings have not tested when phone is off for an extended period of time but looks like it has potential will test more and it does not require root
Edit
After playing some more it seems it does not always work and when it does it opens to the app not my home screen. Kinda annoying well it was worth a shot.
Sent from My Nocturnalized Beast
Click to expand...
Click to collapse
Thanks for the attempt. I hope there is something out there that will help with this issue.

Widgetlocker has this as a setting
Sent from my Nocturnal HOX

JamesR913 said:
Widgetlocker has this as a setting
Sent from my Nocturnal HOX
Click to expand...
Click to collapse
Do you know if Widgetlocker will work on the HTC one X? I thought the volume toggle only works on specific phones.

Widgetlocker works but I am not using that specific function.
Sent from my Nocturnal HOX

pigtaru said:
Do you know if Widgetlocker will work on the HTC one X? I thought the volume toggle only works on specific phones.
Click to expand...
Click to collapse
The "Easy Wake" function on WidgetLocker does not work on the HOX.

Volume Rocker Wake works on CM9 Alpha 5
I've been using CM9 Alpha 5 for a few hours now and it's great !
The first think I set was the Volume Rocker Wake as the Power Button is not as easy to press when using most cases covering the power button.
To enable it, go to SETTING --> DISPLAY --> VOLUME ROCKER WAKE
it enables waking the phone by pressing the volume rocker EITHER up/down.
There is no way to specify one or the other
However, it works great ! I'm really liking CM9, my only complaint is the missing HTC Camera which was just amazing with the hardware burst (I'm still looking for a way to flash it if that's even possible).

As stated above, CM9 is your best bet. Or if AOKP is ever released for the HOX.

Softkey Enabler for XL

Just wondering if there is a mod similar to the Softkey Enabler for the International One X? http://forum.xda-developers.com/showthread.php?t=1797850
I tried that mod on CM10 on my One XL (AT&T) but hit hangs on boot.
Thanks

Ask your fav dev to enable it, I'm not sure why you would want this?
Sent from my HTC One XL using Tapatalk 2

superchilpil said:
Ask your fav dev to enable it, I'm not sure why you would want this?
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
for one. I replaced my screen so I have screen separation issues.
would be nice to enable softkeys (disable soft keys) so that the LEDs from the capacitive buttons don't shine through.

rubensun said:
for one. I replaced my screen so I have screen separation issues.
would be nice to enable softkeys (disable soft keys) so that the LEDs from the capacitive buttons don't shine through.
Click to expand...
Click to collapse
To each their own, I would just disable the backlight on the buttons
Like I said just ask a dev to make a patch, most will be happy to when they have time
Sent from my HTC One XL using Tapatalk 2

Thanks for the info. I'm coming from a Galaxy Nexus, and I like the soft bar. The rotation of the softkeys is nice, and I tend to hit the silkscreen by accident either when holding the phone.
Being a bit new on this forum, any suggestions a dev that may be amenable to requests
Thanks

The hugest reason for enabling soft keys are for iphone people. We are extremely used to having "safe" areas to grab a phone, esp in landscape. I have used an android phone for six months and I don't know where to grab the thing in landscape. I'm always accidentally touching the home or back button and going between apps, it's annoying. And it really hampers usability. This is something that I can't get used to. I definitely think Apple is right to have a hardware old-fashioned home button, or at least some bezel space. This is why I want the soft keys patch for the One XL.

lamenramen said:
The hugest reason for enabling soft keys are for iphone people. We are extremely used to having "safe" areas to grab a phone, esp in landscape. I have used an android phone for six months and I don't know where to grab the thing in landscape. I'm always accidentally touching the home or back button and going between apps, it's annoying. And it really hampers usability. This is something that I can't get used to. I definitely think Apple is right to have a hardware old-fashioned home button, or at least some bezel space. This is why I want the soft keys patch for the One XL.
Click to expand...
Click to collapse
decompile framework-res.apk for the ROM you are using.
I think softkey enabling is in bools.xml.. if not search through strings, arrays, or public.xml
When you find it and change it, recompile and push it to /system/framework

lamenramen said:
The hugest reason for enabling soft keys are for iphone people. We are extremely used to having "safe" areas to grab a phone, esp in landscape. I have used an android phone for six months and I don't know where to grab the thing in landscape. I'm always accidentally touching the home or back button and going between apps, it's annoying. And it really hampers usability. This is something that I can't get used to. I definitely think Apple is right to have a hardware old-fashioned home button, or at least some bezel space. This is why I want the soft keys patch for the One XL.
Click to expand...
Click to collapse
TUTORIAL: How to Turn Off the Hardware Keys - Function, Lights and Vibration
This will work for any AOSP ROM.
1) I used AOKP 4.2.1, you can disable your hardware keys(sort of) editing 2 files in you system/usr/keylayout folder: keypad_8960.kl & synaptics-rmi-touchscreen.kl
Edit these entries in both files, you must open then as a text file and be using a root explorer.
Set key 102, 139, 158, 217 to FOCUS, this will make them do nothing when you are in every app except in camera, when they make it focus.
Save each file after editing and reboot.
2) To turn off vibration go to settings/sound and turn off vibrate on touch.
3) To turn off other hardware key backlights use: AdjBrightness
In AdjBrightness turn off the buttons by pressing the button marked "buttons" under the light toggles. To lock then off so they dont come back on after locking and unlocking, press settings key in that app to bring up a menu, then press Option. Then, under buttons check the first one, "Lock off button lights".
That is it you are done. The only thing is you have it open AdjBrightness after a reboot so it can apply the settings.

superchilpil said:
To each their own, I would just disable the backlight on the buttons
Like I said just ask a dev to make a patch, most will be happy to when they have time
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Try this, worked for me!
https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness
Sent from my HTC One X using xda app-developers app