Brand new One X today and loving it... still trying to get used to the buttons being in a different place than the Galaxy S I..... BUT-
My question is, while powering is there a way to make it so the LED notifications work as normal? It's just stuck on red and i'm not getting other notifications
I'm not sure if this is because of some setting or app that I installed... but I can't find anything in the settings! Thanks for the help
nbshif said:
Brand new One X today and loving it... still trying to get used to the buttons being in a different place than the Galaxy S I..... BUT-
My question is, while powering is there a way to make it so the LED notifications work as normal? It's just stuck on red and i'm not getting other notifications
I'm not sure if this is because of some setting or app that I installed... but I can't find anything in the settings! Thanks for the help
Click to expand...
Click to collapse
That is normal behavior for the light
searley said:
That is normal behavior for the light
Click to expand...
Click to collapse
Thanks. So is there no way to change this?
nbshif said:
Thanks. So is there no way to change this?
Click to expand...
Click to collapse
As of so far no. For all we know someone could put something out there for us. But I understand your frustration!
Sent from my HTC One X using xda premium
Update, I'm working on getting this done now.
I have now found the files in the drivers and I am changing them now
Sent from my HTC One X using xda premium
adamgaltress said:
Update, I'm working on getting this done now.
I have now found the files in the drivers and I am changing them now
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Awesome! I hope you figure it out... I'm kind of surprised this isn't something being discussed more
I've seen a few people talk about it before
Sent from my HTC One X using xda premium
Well it turns out that I will need to compile a kernel to get this to work. So I will slowly push away at trying to get that to work and then post it up on XDA
Sent from my HTC One X using xda premium
I don't have the time, or experience to put together a kernal. However if anyone is ready to make their own 1.28 kernal go here in your source code
drivers>power>power_supply_leds.c
I believe you would need to change this..
Code:
{
union power_supply_propval status;
unsigned long delay_on = 0;
unsigned long delay_off = 0;
if (psy->get_property(psy, POWER_SUPPLY_PROP_STATUS, &status))
return;
dev_dbg(psy->dev, "%s %d\n", __func__, status.intval);
switch (status.intval) {
case POWER_SUPPLY_STATUS_FULL:
led_trigger_event(psy->charging_full_trig, LED_FULL);
led_trigger_event(psy->charging_trig, LED_OFF);
led_trigger_event(psy->full_trig, LED_FULL);
led_trigger_event(psy->charging_blink_full_solid_trig,
LED_FULL);
break;
case POWER_SUPPLY_STATUS_CHARGING:
led_trigger_event(psy->charging_full_trig, LED_FULL);
led_trigger_event(psy->charging_trig, LED_FULL);
led_trigger_event(psy->full_trig, LED_OFF);
led_trigger_blink(psy->charging_blink_full_solid_trig,
&delay_on, &delay_off);
break;
default:
led_trigger_event(psy->charging_full_trig, LED_OFF);
led_trigger_event(psy->charging_trig, LED_OFF);
led_trigger_event(psy->full_trig, LED_OFF);
led_trigger_event(psy->charging_blink_full_solid_trig,
LED_OFF);
break;
}
}
static int power_supply_create_bat_triggers(struct power_supply *psy)
{
int rc = 0;
psy->charging_full_trig_name = kasprintf(GFP_KERNEL,
"%s-charging-or-full", psy->name);
if (!psy->charging_full_trig_name)
goto charging_full_failed;
psy->charging_trig_name = kasprintf(GFP_KERNEL,
"%s-charging", psy->name);
if (!psy->charging_trig_name)
goto charging_failed;
psy->full_trig_name = kasprintf(GFP_KERNEL, "%s-full", psy->name);
if (!psy->full_trig_name)
goto full_failed;
psy->charging_blink_full_solid_trig_name = kasprintf(GFP_KERNEL,
"%s-charging-blink-full-solid", psy->name);
if (!psy->charging_blink_full_solid_trig_name)
goto charging_blink_full_solid_failed;
led_trigger_register_simple(psy->charging_full_trig_name,
&psy->charging_full_trig);
led_trigger_register_simple(psy->charging_trig_name,
&psy->charging_trig);
led_trigger_register_simple(psy->full_trig_name,
&psy->full_trig);
led_trigger_register_simple(psy->charging_blink_full_solid_trig_name,
&psy->charging_blink_full_solid_trig);
goto success;
charging_blink_full_solid_failed:
kfree(psy->full_trig_name);
full_failed:
kfree(psy->charging_trig_name);
charging_failed:
kfree(psy->charging_full_trig_name);
charging_full_failed:
rc = -ENOMEM;
success:
return rc;
}
Into this..
Code:
{
union power_supply_propval status;
unsigned long delay_on = 0;
unsigned long delay_off = 0;
if (psy->get_property(psy, POWER_SUPPLY_PROP_STATUS, &status))
return;
dev_dbg(psy->dev, "%s %d\n", __func__, status.intval);
switch (status.intval) {
case POWER_SUPPLY_STATUS_FULL:
led_trigger_event(psy->charging_full_trig, [B]LED_OFF[/B]);
led_trigger_event(psy->charging_trig, LED_OFF);
led_trigger_event(psy->full_trig,[B] LED_OFF[/B]);
led_trigger_event(psy->charging_blink_full_solid_trig,
LED_OFF);
break;
case POWER_SUPPLY_STATUS_CHARGING:
led_trigger_event(psy->charging_full_trig, [B]LED_OFF[/B]);
led_trigger_event(psy->charging_trig, [B]LED_OFF[/B]);
led_trigger_event(psy->full_trig, LED_OFF);
led_trigger_blink(psy->charging_blink_full_solid_trig,
&delay_on, &delay_off);
break;
default:
led_trigger_event(psy->charging_full_trig, LED_OFF);
led_trigger_event(psy->charging_trig, LED_OFF);
led_trigger_event(psy->full_trig, LED_OFF);
led_trigger_event(psy->charging_blink_full_solid_trig,
LED_OFF);
break;
}
}
any update on this?
in all previous htc phones that i had it was normal that LED was changing clours on notifications when charging. what happened with HOX?...
deadwilder said:
any update on this?
in all previous htc phones that i had it was normal that LED was changing clours on notifications when charging. what happened with HOX?...
Click to expand...
Click to collapse
Accidentally pressed like instead of quote, but my final update on this was in my previous post on here. You need to contact a kernel developer
Sent from my HTC One X using xda premium
Related
Hi all,
as you can see in this video,
http://android.hdblog.it/2010/06/20...a-della-presentazione-italiana-del-24-giugno/
Click to expand...
Click to collapse
there are two backlighted bottons on our Galaxy S; once is the BACK botton, the second one is OPTIONS botton.
Now, probably we can remap the OPTIONS botton for use it like a NOTIFICATION LED!
I suppose that: if we have one message/email or one unaswered call, the light of the option botton could PULSE..!!!
I think that this is the best solution for our NON-LEDED-PHONE...
What do you think?? Probably we can work on!!
Let me know!!
great idea.. definitely worth it..
one thing nice about i9000 is the home button wakes the phone
raspdeep said:
great idea.. definitely worth it..
one thing nice about i9000 is the home button wakes the phone
Click to expand...
Click to collapse
Thanks mate, i've contacted OBrian, as soon as possible I start to try and work on it...
First of all i need the source but i don't know why i cant download it from samsung. Somebody can upload the source on another server?
Second, i'll try to find the files that map the bottons
In the end, if is possible (but i need the help of our cheefs) i can work on it...
Waitin'...
socket84 said:
Thanks mate, i've contacted OBrian, as soon as possible I start to try and work on it...
First of all i need the source but i don't know why i cant download it from samsung. Somebody can upload the source on another server?
Second, i'll try to find the files that map the bottons
In the end, if is possible (but i need the help of our cheefs) i can work on it...
Waitin'...
Click to expand...
Click to collapse
definitely worth it !!!!!! thank you in advance
Archius said:
definitely worth it !!!!!! thank you in advance
Click to expand...
Click to collapse
If somebody wants to help me, is appreciated!!
Fist of all we have to discover where the botton configuration files are..
Great Idea i'll download the source and try for a look but im not too good
it will take a while, till the file ist uloaded but i'll edit my post and add the link
is netload ok ?
Jonas.M said:
it will take a while, till the file ist uloaded but i'll edit my post and add the link
is netload ok ?
Click to expand...
Click to collapse
Thanks man, never mind, i've downloaded it... I'm searching the files...
kk i'm searching too
Jonas.M said:
kk i'm searching too
Click to expand...
Click to collapse
Tried to search "key", there are alot of file in kernel folder, but they seems to be unusefull...
Probably we need a dump, not the source...
Searchin'....
does it light up while booting?
Jonas.M said:
does it light up while booting?
Click to expand...
Click to collapse
I don't know... I'm waitin' two Galaxy S for early July, so we need to wait somebody that have the phone right now...
But i can search on youtube...
it seams, that they only light up if you use them
but i cant find any video that shows the booting properly
Jonas.M said:
it seams, that they only light up if you use them
but i cant find any video that shows the booting properly
Click to expand...
Click to collapse
Yes, but they light up, i think this is enough
I saw a video of the boot on youtube but i don't find it... damn!
Boot:
http://www.youtube.com/watch?v=n_G51c7hxbU
Click to expand...
Click to collapse
No lights up...but maybe the part of the video that we need is too short..
They do not light up under the boot.
But you can trigger them/use them while booting.
Elinsa said:
They do not light up under the boot.
But you can trigger them/use them while booting.
Click to expand...
Click to collapse
Probably, but we need to activate them any time we loose a call or we have a message/email...
I see that the bottons are capacitives, not phisicals...
Yes, they are touchbuttons. If you need any help from me since I have the phone already let me know.
Code:
case ACPI_BUTTON_NOTIFY_STATUS:
input = button->input;
if (button->type == ACPI_BUTTON_TYPE_LID) {
acpi_lid_send_state(button);
} else {
int keycode = test_bit(KEY_SLEEP, input->keybit) ?
KEY_SLEEP : KEY_POWER;
input_report_key(input, keycode, 1);
input_sync(input);
input_report_key(input, keycode, 0);
input_sync(input);
}
acpi_bus_generate_proc_event(button->device, event,
++button->pushed);
break;
is the KEY_SLEEP the back key ?
Jonas.M said:
Code:
case ACPI_BUTTON_NOTIFY_STATUS:
input = button->input;
if (button->type == ACPI_BUTTON_TYPE_LID) {
acpi_lid_send_state(button);
} else {
int keycode = test_bit(KEY_SLEEP, input->keybit) ?
KEY_SLEEP : KEY_POWER;
input_report_key(input, keycode, 1);
input_sync(input);
input_report_key(input, keycode, 0);
input_sync(input);
}
acpi_bus_generate_proc_event(button->device, event,
++button->pushed);
break;
is the KEY_SLEEP the back key ?
Click to expand...
Click to collapse
No, this is the sleep/power phisical button...
Could anyone explain me a bit on how to get the white and color screen away on the kaiser when turning on the screen?
I've seen a post called vsync tuning where a dude didn't get the screen anymore with editing the fake vsync count but I've tried a lot of diffrent numbers and it doesn't seem to affect my phone.
Any help?
There is something bad with LCD Drivers. It happens to all of us, the Bright White Flicker effect when bringing device to wake up (after HTC boot logo and when we wake up device from standby). Though screen fades out nicely when we put it to sleep mode. Its really eye irritating, when I want to see time at night
Indeed, and I'm wondering if it's possible to fix this with the fake_vsync.
syntax1993 said:
Indeed, and I'm wondering if it's possible to fix this with the fake_vsync.
Click to expand...
Click to collapse
umm can u guide me to that post? I really want to fix it as well. Kinda makes my buddies think that I am using a pirated OS or like that
Found here:
http://forum.xda-developers.com/showthread.php?p=9373697
syntax1993 said:
Found here:
http://forum.xda-developers.com/showthread.php?p=9373697
Click to expand...
Click to collapse
I used ADB.exe with ADBWinApi.dll, connected my phone with USB debugging.
I issued:
adb shell "echo 15 > /sys/module/msm_fb/parameters/fake_vsync_count"
Click to expand...
Click to collapse
The white screen still flickers, but the gibberish screen stays for somehow less moments.
used 25, flicker is still there, gibberish screen disappears for most of the wake ups
used 30, same as above
used 40, same as above
Can't get the white screen to disappear
I've found this:
http://gitorious.org/nushrike-hd2-a...mmit/8b879aa357ecfbd5a9ba07d0f866637fe9724112
mdp_lcdc patch for HTC Leo, http://gitorious.org/nushrike-hd2-a...b879aa357ecfbd5a9ba07d0f866637fe9724112.patch
please if someone can tell us what these things do -.-
drivers/video/msm/mdp_lcdc.c | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/video/msm/mdp_lcdc.c b/drivers/video/msm/mdp_lcdc.c
index e0f44f6..e7a0467 100644
--- a/drivers/video/msm/mdp_lcdc.c
+++ b/drivers/video/msm/mdp_lcdc.c
@@ -353,9 +353,10 @@ static int mdp_lcdc_probe(struct platform_device *pdev)
lcdc->fb_panel_data.suspend = lcdc_suspend;
lcdc->fb_panel_data.resume = lcdc_resume;
lcdc->fb_panel_data.wait_vsync = lcdc_wait_vsync;
-#if defined(CONFIG_MACH_HTCLEO)
- // Temporarily disable vsync to prevent a scheduler bug, need
- // to be looked into further.
+#if defined(CONFIG_FRAMEBUFFER_CONSOLE)
+ // Use fake vsync when the framebuffer console is enabled. If we do not do this, the
+ // driver will perform scheduling in interrupt context.
+ #warning Enabling fake vsync as FRAMEBUFFER_CONSOLE is enabled
lcdc->fb_panel_data.request_vsync = 0;
#else
lcdc->fb_panel_data.request_vsync = lcdc_request_vsync;
Click to expand...
Click to collapse
hmm
i opened with the file explorer and i didnt find any fake vsync file
Meh wants to fix this, too
u need
dude u need ADB.exe and AdbWinApi.dll to edit that value!
Hey
I'm looking for an app that can start the dock app or any app just by placing a magnet near the magnetic-field senor. (Like the droid).
I placed a normal magnet at the backcover of my arc and in "sensor test" the third value of the magnet sensor went up to 1300 (normaly not more than 30). So should work...
Anybody an idea where to get that or anyone wanna code that?
Thanks
Does nobody has an idea?
Sent from my LT15i using XDA App
--Rob-- said:
Does nobody has an idea?
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
i'll take a look at it....
the question is to launch the standart app for cardock
Code:
<category android:name="android.intent.category.CAR_DOCK"/>
if magnet sensor went up to 1300 ..... right ?
yes, goes up to 1300, but it would work if u define the border at 300 or something like this. In normal environment it barly goes over 30...
An option to choose an installes app would be the best solution I guess.
If u can copy&paste the code to choose a diffrent app at -300 would make the phone like the droid (put at charge dock => clock or whatever; put at car dock => car app).
Just some ideas. I guess there would be a great market, if u sell the prog in the market for 1€ or 1,50€.
Thanks
Anything new??
i build it into my app setxperia because its has to be running in a service and in this project ive allready a suitable framework
here a first test version.
what it does:
Code:
if (MagneticField > 120 && mgr.getCurrentModeType() != Configuration.UI_MODE_TYPE_CAR ) {
mgr.enableCarMode(UiModeManager.ENABLE_CAR_MODE_GO_CAR_HOME);
}else if(MagneticField < 100 && mgr.getCurrentModeType() == Configuration.UI_MODE_TYPE_CAR ){
mgr.disableCarMode(UiModeManager.DISABLE_CAR_MODE_GO_HOME);
}
setXperia shows the current MagneticField in the notify bar (i.e. " ... MF:51")
for testing i installed CarDockv3 https://market.android.com/details?id=net.cwfk.ig88.carhome3 on my phone but it work with any similar soft
has anyone test it ? i personally have problems with krusell case because it has magnetic closeing ...
next version comes with fully cusomizable value for CarModeOn and CarModeOff and it also switch to carmode only if display is ON to overcome the case problem.
curently im testing this out, any comments on tests from you are welcome
Sorry, didn't c ur post. I'll try it out tonight then giving you feedback.
Hey,
I'm also looking for something similar.
I'd like it to set a profile when detecting a magnet (to set the ring volume and the media volume to high in the car).
edit: forgot to say i use a Xperia ARC
I was developing on another T3 device and come across some things that might come in handy for the one x specifically build.prop.
Within build.prop I found this:
debug.nfc.fw_download : Currently set to false but can be enabled by setting to true
debug.nfc.se: Set to false, debugging, to do with tegra3 built in security engine (se)
media.tegra.max.out.channels: ?
mediea.tegra.out.channel.map: ?
net.qtaguid_enabled = 1/0, self explanatory
persist.sys.NV_FPSLIMIT = 35 (change to 60, for 60fps ui?)
persist.sys.NV_POWERMODE = 1
persist.sys.NV_PROFVER = 15
persist.sys.NV_STEREOCTRL = 0
persist.sys.NV_STEREOSEPCHG = 0
persist.sys.NV_STEREOSEP = 20
persist.sys.ui.hw = true (hw accelerated UI(Should already be set to true on ICS))
persist.tegra.NV_FPSLIMIT = 0 ? (unsure why there's 2 of them)
persist.tegra.nvmmlite = 1 (Unsure)
power.saving.mode = 0
ro.bootmode [unknown]
ro.factorytest = 0
ro.bootloader [unknown]
Persist.sys.fw.camera.status = 1
Persist.dmesg.mode = split
Persist.dmesg.rotate = 1
Drm.service.enabled = 1/0
Enjoy
shaky156 said:
persist.tegra.nvmmlite = 1 (Unsure)
Click to expand...
Click to collapse
Just so you know, changing this to 0 breaks the camera. No idea what it actually does though
I added everything else in your first post to my build.prop and all that seemed to change was that my quadrant score dropped by about 700 (4900 or so, to 4200). Actual phone speed didn't seem to drop, but I'll have a play around with them some more and see what happens
Improvements ?
Hi,
Thanks for the information.
Could you please let us know what are the improvements we can expect after this.??
Regards,
mahesh_9j said:
Hi,
Thanks for the information.
Could you please let us know what are the improvements we can expect after this.??
Regards,
Click to expand...
Click to collapse
I havent tested modifying those, i cant test them lol, but changing fps limit should change ui fps, afaik its currently set to 35fps
Changing nvpowermode to 0 might stop the lower freq clks when batterys lower
Sent from my Desire HD
shaky156 said:
I havent tested modifying those, i cant test them lol, but changing fps limit should change ui fps, afaik its currently set to 35fps
Changing nvpowermode to 0 might stop the lower freq clks when batterys lower
Sent from my Desire HD
Click to expand...
Click to collapse
The "persist.says.NV_FPSLIMIT" works nicely! Set it to 10 or so to make the UI almost unusable! Only works for the phone UI though, doesn't alter application fps.
Not sure how to measure how fast it can go though.
Sent from my HTC One X using xda premium
Meltus said:
The "persist.says.NV_FPSLIMIT" works nicely! Set it to 10 or so to make the UI almost unusable! Only works for the phone UI though, doesn't alter application fps.
Not sure how to measure how fast it can go though.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Best to set it to 60
Sent from my Desire HD
shaky156 said:
Best to set it to 60
Sent from my Desire HD
Click to expand...
Click to collapse
Is it already in HOX's build.prop or should we just add the lines that we want?
mach0boi said:
Is it already in HOX's build.prop or should we just add the lines that we want?
Click to expand...
Click to collapse
It's already in build.prop, just search and edit the value to 60.
double_ofour said:
It's already in build.prop, just search and edit the value to 60.
Click to expand...
Click to collapse
Naduduling na ko.
Tried and tried still can't find it. There's only a few lines in here that starts with "persist.". BTW, i'm on insertcoin.
mach0boi said:
Naduduling na ko.
Tried and tried still can't find it. There's only a few lines in here that starts with "persist.". BTW, i'm on insertcoin.
Click to expand...
Click to collapse
If its not there
Add it in, im sure all chefs will add it in when updating their roms
Sent from my Desire HD
shaky156 said:
If its not there
Add it in, im sure all chefs will add it in when updating their roms
Sent from my Desire HD
Click to expand...
Click to collapse
Already did. IDK if it's a placebo or have a real effect on the UI. Well i guess having it in here won't hurt
mach0boi said:
Already did. IDK if it's a placebo or have a real effect on the UI. Well i guess having it in here won't hurt
Click to expand...
Click to collapse
Few post above youra, Meltus tested the nvfpslimit, it works
Sent from my Desire HD
mach0boi said:
Already did. IDK if it's a placebo or have a real effect on the UI. Well i guess having it in here won't hurt
Click to expand...
Click to collapse
Have you tried lowering the value down? lets say like 10 if it slows down the UI? if not then maybe that line has no effect at all..
s-off ka pre? ineedit mo directly sa /system/? hehe.. or paflash2 ng script sa recovery?
shaky156 said:
Few post above youra, Meltus tested the nvfpslimit, it works
Sent from my Desire HD
Click to expand...
Click to collapse
well.. that answers our question.
double_ofour said:
Have you tried lowering the value down? lets say like 10 if it slows down the UI? if not then maybe that line has no effect at all..
s-off ka pre? ineedit mo directly sa /system/? hehe.. or paflash2 ng script sa recovery?
Click to expand...
Click to collapse
PM
10 chars
Ill update this soon
Sent from my Desire HD
mach0boi said:
Naduduling na ko.
Tried and tried still can't find it. There's only a few lines in here that starts with "persist.". BTW, i'm on insertcoin.
Click to expand...
Click to collapse
to search use terminal app... then type the command
getprop | grep "thing to search"
or if you're sure of the exact key and just want to check the value use
getprop "exact.key"
double_ofour said:
It's already in build.prop, just search and edit the value to 60.
Click to expand...
Click to collapse
Consider the fact that upping UI FPS from 30 to 60 doubles the GPU workload and results in battery hit.
this value definitely works in controlling the launcher FPS
persist.sys.NV_FPSLIMIT = 60
however the line is not there by default, so it might be already 60fps default
placing the file with low value will cap the FPS
Shaky any idea how to force Tegra full quad performance mode?
hamdir said:
this value definitely works in controlling the launcher FPS
persist.sys.NV_FPSLIMIT = 60
however the line is not there by default, so it might be already 60fps default
placing the file with low value will cap the FPS
Shaky any idea how to force Tegra full quad performance mode?
Click to expand...
Click to collapse
Might have an idea, ill let you know once im abit more free
Sent from my HTC Desire HD
Opening this thread to find a solution to keyboard backlights not working on JB ROMs, if the phone is put on in any other mode other than autobrightness.
I might try possible things to make this work and post here about the changes I made, which can help save time for others trying to solve this bug.
If anybody has any ideas about where to look and what can be a solution they are welcome to reply and contribute.
Update 05 Jan : See post http://forum.xda-developers.com/showpost.php?p=36311016&postcount=11
Since I haven't seen the files myself, I could be talking complete BS here, but...
When looking at the code in the OP of thegreatergood's post the name of the integer-array seems to imply the KeyboardBacklightValues are linked to config_autoBrightness. Although I would expect a dot between those two if KeyboardBacklightValues is truly a child of config_autoBrightness... Java, and all...
Code:
<integer-array name="config_autoBrightnessKeyboardBacklightValues">
<item>255</item>
<item>255</item>
<item>255</item>
<item>255</item>
<item>0</item>
</integer-array>
Looking at [GUIDE][HOW-TO][ANY-ROM]Change Auto Brightness Levels elsewhere on XDA it would indeed seem this only sets what the backlight does in response to various auto-detected light conditions in auto-brightness mode, and NOT for manual brightness.
If so, using the same syntax, there might be something like "config_brightnessKeyboardBacklightValues" or "config_manualBrightnessKeyboardBacklightValues" somewhere? Or that should be inserted somewhere...? Perhaps a search for lines with "config" and "Brightness" and "Values" may provide more inspiration...?
Again, the above might be total BS as I haven't looked in the file myself. I'm still planning on getting more involved hands-on, but that'll have to wait for a few more days!
On that note, Happy 2013!
Evil Alex said:
Since I haven't seen the files myself, I could be talking complete BS here, but...
When looking at the code in the OP of thegreatergood's post the name of the integer-array seems to imply the KeyboardBacklightValues are linked to config_autoBrightness. Although I would expect a dot between those two if KeyboardBacklightValues is truly a child of config_autoBrightness... Java, and all...
Code:
<integer-array name="config_autoBrightnessKeyboardBacklightValues">
<item>255</item>
<item>255</item>
<item>255</item>
<item>255</item>
<item>0</item>
</integer-array>
Looking at [GUIDE][HOW-TO][ANY-ROM]Change Auto Brightness Levels elsewhere on XDA it would indeed seem this only sets what the backlight does in response to various auto-detected light conditions in auto-brightness mode, and NOT for manual brightness.
If so, using the same syntax, there might be something like "config_brightnessKeyboardBacklightValues" or "config_manualBrightnessKeyboardBacklightValues" somewhere? Or that should be inserted somewhere...? Perhaps a search for lines with "config" and "Brightness" and "Values" may provide more inspiration...?
Again, the above might be total BS as I haven't looked in the file myself. I'm still planning on getting more involved hands-on, but that'll have to wait for a few more days!
On that note, Happy 2013!
Click to expand...
Click to collapse
Happy 2013 to you and all the glide community as well.
The file has no more settings and the code is correct, but I was thinking of taking apart ICS where it all worked perfect and do a compare on all files related to keyboard lights. Hope fully would get a clue.
Sent from my SGH-I927 using xda app-developers app
you may wanna take a look at settings.apk, services.jar and android-policy.jar they all have brightness control stuff in em ... but it may be in smali which we all love.... the stock samsung brightness settings controls the duration which the lights are on .... and thats whats missing in aosp...
thegreatergood said:
you may wanna take a look at settings.apk, services.jar and android-policy.jar they all have brightness control stuff in em ... but it may be in smali which we all love.... the stock samsung brightness settings controls the duration which the lights are on .... and thats whats missing in aosp...
Click to expand...
Click to collapse
Thx will surely give it a try .
Sent from my SGH-I927 using xda app-developers app
ninthsense said:
Thx will surely give it a try .
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
If you think about it that could be a cool feature for users to make it like a cars headlights but it would need to be a option in the settings. need a toggle in settings however
Cory_branch said:
If you think about it that could be a cool feature for users to make it like a cars headlights but it would need to be a option in the settings. need a toggle in settings however
Click to expand...
Click to collapse
A car's headlights? How do you mean?
I think he wants it to be at a different brightness like a dimmer.
Sent from my SGH-I927 using xda app-developers app
Laugher19 said:
I think he wants it to be at a different brightness like a dimmer.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I have only seen the keyboard backlights be full on or full off. I have never seen them dim or fade. If they did have some staging that I never noticed or could be worked into the auto brightness then that would be news to me.
QuickSilverAWD said:
I have only seen the keyboard backlights be full on or full off. I have never seen them dim or fade. If they did have some staging that I never noticed or could be worked into the auto brightness then that would be news to me.
Click to expand...
Click to collapse
Not dim or fade, but with the new fix the keyboard backlight now works on auto brightness mode depending on the light sensor in the phone. So if it's dark enough then the keyboard lights will come on and if its daylight then it remains off. Works pretty well in real life situations.
Sent from my SGH-I927 using xda app-developers app
I've worked out a patch using the info on this thread http://forum.xda-developers.com/showthread.php?t=661343 . This is a very crude way of fixing it but until it's really fixed in the JB roms this can be useful, specially CM10.1 .
So here is how to run it.
Unzip this file Download, put the script in your sdcard either through adb push or file manager. Pull up the terminal app and type the following :
Code:
su [press enter]
nohup bash /sdcard/Kbonoff.sh > /dev/null &
Then you can leave the terminal and guess what the keyboard backlight will work now.
This will only work until your next reboot. Once you guys test it, i'll probably look into making it more permanent. Don't want to have a permanent fix which drains battery and affects performance.
Note : I only tested it on dman's CM10
Keept it running a full day and i see no visible impact on performance or battery.
This works great. I can also see no significant drop in performance or battery life. I do have a lag in the time the lights take to come on. The only bug I really see is that when the keyboard is open and your phone locks. You have to close and reopen the keyboard for the lights to come back on. But it may be just me. Anyways great job and keep up the good work! :thumbup:
Sent from my cm10.1 wonder
jevan24 said:
This works great. I can also see no significant drop in performance or battery life. I do have a lag in the time the lights take to come on. The only bug I really see is that when the keyboard is open and your phone locks. You have to close and reopen the keyboard for the lights to come back on. But it may be just me. Anyways great job and keep up the good work! :thumbup:
Sent from my cm10.1 wonder
Click to expand...
Click to collapse
Nope not a bug really. The script works on a simple code.. when it find a keypress generated on slide out, it lights up the keyboard and when its slide in it switches it off.
I've tried and yes when it gets locked and screen is off it gets switched off. I'll try to see in logcat if I can watch for anything unique for the slide out and in only.
Report back if somebody has tried it on a diff jellybean rom.
Sent from my SGH-I927 using xda app-developers app
I'm running dman's CM 10.1 [4.2.1] Beta-2 for I927 and kb script doesn't work ;/
I'm running dmans cm 10.1 and everything works here..
Sent from my cm10.1 wonder
---------- Post added at 07:22 PM ---------- Previous post was at 07:00 PM ----------
I have also found that at least for me they will time out and not come back on even with the screen awake and im still typing... I will try to get some logcats when i get some extra time. Probably later after i get off work. It also seems thegreatergood found something out for cm 10.1. Cheers guys! :beer:
Sent from my cm10.1 wonder
Running KB script causes:
I/BootReceiver( 430): Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
I/DEBUG ( 103): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 103): Build fingerprint: 'samsung/SGH-I927/SGH-I927:4.0.4/IMM76D/UCLG9/test-keys'
I/DEBUG ( 103): Revision: '14'
I/DEBUG ( 103): pid: 8603, tid: 8603, name: awk >>> awk <<<
I/DEBUG ( 103): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000dff
or:
I/DEBUG ( 103): memory map around fault addr 000214f4:
I/DEBUG ( 103): (no map below)
I/DEBUG ( 103): 00008000-00080000 /system/xbin/busybox
I/DEBUG ( 103): 00080000-00082000 /system/xbin/busybox
F/libc ( 9946): Fatal signal 11 (SIGSEGV) at 0x00000df8 (code=1), thread 9946 (awk)
Are you running it with root ? Also on which rom and which kernel /
Sent from my SGH-I927 using xda app-developers app
ninthsense said:
Are you running it with root ? Also on which rom and which kernel /
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Of course i'm running it as root.. Rom is dmans cm 10.1 with covenant kernel.
Here some part of /main log: http://pastebin.com/wHMr8WgL
And the system log: http://pastebin.com/AYgyDh6W
In Paranoid Android you can change the auto dim settings so that the keyboard light is always on in advanced display settings.