Anyone come across a place in the code where you can configure the brightness of the light behind the hardware keyboard and the hardware buttons on the face?
Here's the deal, the buttons on the front facing of the phone are just too damn bright, and now that I have one of those privacy-shield screen protectors on (love it, btw) the hardware buttons are way too bright, about 3 times the level of light that emanates from the screen.
I desperately need to figure out how to dim those front face buttons, because it's really screwing with my eyes while i'm trying to work with the device.
Everything I search for on XDA comes up with using the hardware buttons to set the brightness levels, but nothing about setting the brightness levels of the backlit buttons themselves.
While we're poking around on it I figured we should see about the brightness level of the hardware buttons on the keyboard, too. I think they're fine, but someone else might want to adjust it and it stands to reason to concentrate the info all in one spot.
Anyone come up with a clue while browsing through the device, or know how to do this? I don't want to lose all the illumination, just dim it a bit.
Thanks!
Clue 1:
In kernel source, /arch/arm/mach-msm/board-doubleshot.c
Around line 2300 some info defined.
More as it's found, going through all kernel source line by line takes a while.
Related
I really like the look of the cruise. And the glowing circle around the center button on the DPAD is cool. However, it is really bright! Especially at night if you are reading in the dark.
Is there a way to toggle this on or off? Or even better to control the brightness.
Thanks for your suggestions.
No one knows how to control this?
I 'd be interested in knowing how to lower the brightness too !
I got my new S740 today, and I'm pretty happy with it. 1 annoying function is that the number pad doesn't light up until you press a key. Even when you direction pad or the home/back button is doesn't light up.
That may not sound that bad, they there is very little distinction via feel to the buttons on the number pad, which forces you to hit a random key (usually the wrong one) to get it to light up.
Anyone know a way around that?
Probably ask in the ROSE forum^^
Otherwise I think you could try to disable the light sensor, so it lights up right away when you press a button.
Is there a Rose forum, I looked but did't see it. I saw a few other 740 posts in this forum so assumed that is where people are posting for it.
I tried disableing the light sensor, but same issues, the phone lights up on the dpad not the number pad until I push a number.
this is the Rose forum:
click
I was looking under smartphones, I wonder why it isn't under smartphones.
Have the same aggravation with it.
What the hell was the engineer thinking!?!
This is the only thing about the phone I am upset with and it's one of these things that you can't believe it's even an issue. I mean the light up scheme on every htc phone prior to this was FINE.
Someone just got way to clever and over engineered this bit.
If you hit the d pad nothing lights up. If you hit the home/back/softkeys area that section lights up, but if you want to light the keypad you have to press someting. Plus it turns off VERY quickly. I can't find any settings for this other than sensor which has zero effect.
Some admin needs to slide this over to the very quiet ROSE forum I guess.
Sorry if this has been covered already; I searched but didn't find anything, but then I may not know the right terms.
My question is: is there a hack or app to adjust when the hard buttons illuminate? I always forget they're there, and when I do remember I still have to look at the buttons. What I'd really like is to make them light up whenever the dial pad comes up or maybe even when the screen is fully illuminated (not staying on when the screen goes a little dim when you don't touch it for a while). I'd also like to be able to change the hardware Windows button to go back to the Sense home screen, rather than the Start menu.
i use KeypadLedControl, it enables the hardware buttons to light up whenever the screen is on
Excellent, thank you!
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.
Does anyone have the same issue as me? Every few minutes, the navigation buttons slightly move to a different position on the screen, which makes them off-center with the rest of the screen. This usually happens after locking and unlocking the phone. I have tried to restart the phone into the safe mode but the issue is still present there. I have even contacted Sony support.
My oled TV does this to prevent burn in. Maybe check the display settings to see if it is such a feature?
Not sure, I cant find anything like that in display settings. I have also tried to change the minimum screen dpi in the developer settings and it fixed it right after the change, but as soon as I lock and unlock the phone, the buttons are off-center again.
This is a feature. It moves them over time to avoid burn in.
Ok thanks. But if this is a feature, it's pretty annoying, as it's very visible at times. Why aren't the buttons rather changing their size a bit instead? It would be less noticeable then moving them from side to side.
Nevermind, I have disabled the dock and I can't notice it anymore ?