Hi,
I'm currently on a CM Build and the CM-Feature for changing light sensor levels is not working.
I know that this will make led notifications not work anymore.
But I would like to test how much this can improve my battery life.
Please don't tell me "turn auto backlight off to save battery" or "this will disable led notifications"... I'm aware of the pro's and con's and it is just a test for me...
So could someone please tell me which files I need to replace and where can I find them?
Thx in advance!
I'm also using the working lights lib...
LED notifications isn't that important for me.
The name of the file is different from rom to rom, so ensure you name it correctly and replace it in system/lib/hw.
Also don't forget to set the right permissons.
j4n87 said:
I'm also using the working lights lib...
LED notifications isn't that important for me.
The name of the file is different from rom to rom, so ensure you name it correctly and replace it in system/lib/hw.
Also don't forget to set the right permissons.
Click to expand...
Click to collapse
Thx. I tried this file. Renamed it, moved it with RootExplorer. Set Permission to rw-r--r--. Rebooted. edited light sensor levels with cyanogenmod-settings. taped save and apply. but it does not work. when i press reload current they are back to default values. alo tried reeboot after save and apply. But with the same result.
Is there anything I did wrong??
Did youu checked your pm? =)
Related
I've got a question: when my TyTN was in for repair, I used a Nokia E61. It had a cool feature:
whenever you don't use the device for 30 seconds, the backlight would "fade out" to the minimum (not 0, but 1 on a scale of 10). Now that I have my TyTN back; I sort of "miss" that in my TyTN. Is ot possible to create something that would do this?
Ooh. That is a pretty cool feature.
I second the request.
Suprised I haven't seen that yet.
that means an process should always regulate the backlight and but it back to maximum as soon as an input happens. sound a bit like wasted cpu load
edit: i want it! ^_^
Great feature, have you tried this plugin
no files...
borealcool said:
Great feature, have you tried this plugin
Click to expand...
Click to collapse
IWhen I extract your attachement I only find the readme file.
Or am I doing something wrong?
What I read in the readme file is excactly what I meant!
stynos said:
IWhen I extract your attachement I only find the readme file.
Or am I doing something wrong?
What I read in the readme file is excactly what I meant!
Click to expand...
Click to collapse
Try again. I downloaded it and has 3 files in the zip.
no luck...
CameoTabby said:
Try again. I downloaded it and has 3 files in the zip.
Click to expand...
Click to collapse
Nope, tried everything (even extracting it on my TyTN, but all I get is the readme-file. Could someone perhaps pm me?
stynos said:
Nope, tried everything (even extracting it on my TyTN, but all I get is the readme-file. Could someone perhaps pm me?
Click to expand...
Click to collapse
Extract and turn on show system hidden files. Then You will see all files.
nikolica said:
Extract and turn on show system hidden files. Then You will see all files.
Click to expand...
Click to collapse
mmm on my PC I have this option switched on. Tried it with Resco Explorer on the TyTN, and who could have guessed: I have the files.
Now the next issue: where do I put them? Tried the /windows directory, but I thought it better not to replace the existing backlight.exe without "proper guidance". Anyone has experience?
<edit> Heck, tried it anyway. I can't open the backlight settings now... (thank god I made a copy of the original backlight.exe).
Any advice?
stynos said:
Heck, tried it anyway. I can't open the backlight settings now...
Click to expand...
Click to collapse
If it disabled your backlight setting that's a good sign, there must be another file referenced in the mui which needs to be included. Can someone point me in the right direction?
Stynos I sure hope you did do a backup of your old backlight files. If you haven't, you can probably get them back with recovery software or from someone with a TyTN. I should of added a warning, just thought it went without mentioning.
removing these "new" files and soft reset should restore system ones.....ehhh..
btw, it is not working on wizard, too...
There's another files in the directory called "backlight.dll" maybe include that one too.
the.hacker.x said:
There's another files in the directory called "backlight.dll" maybe include that one too.
Click to expand...
Click to collapse
No such file, did find this one though...
I loaded the power_service.dll and the backlight control panel app still doesn't work on my HTC Apache. The Power icon still works perfectly.
My power registry looks like this:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State
BacklightOff
ColdReboot
On
Reboot
+Resuming
+ScreenOff
+Suspend
+Unattended
+UserIdle
Mine is the same.
the.hacker.x said:
Mine is the same.
Click to expand...
Click to collapse
What option tabs do you have under Settings/System/Backlight ?
I've got |Brightness|Battery power|External power|
In Settings/System/Power I have |Battery|Advanced|
If you've got these same settings, one of them might be conflicting with the other.
For example I've got Settings/System/Power|Advanced| "On battery power" set to "Turn off device if not used for 5 minutes"
Then in Settings/System/Backlight|Battery power| set to "Turn off backlight if device is not used for 30 sec
The last setting just lowers the backlight
borealcool said:
What option tabs do you have under Settings/System/Backlight ?
I've got |Brightness|Battery power|External power|
In Settings/System/Power I have |Battery|Advanced|
If you've got these same settings, one of them might be conflicting with the other.
For example I've got Settings/System/Power|Advanced| "On battery power" set to "Turn off device if not used for 5 minutes"
Then in Settings/System/Backlight|Battery power| set to "Turn off backlight if device is not used for 30 sec
The last setting just lowers the backlight
Click to expand...
Click to collapse
Your last setting is "Turn off backlight", I thought it would add an option to dim the screen to a lower backlight setting. Because I have the turn off backlight feature
the.hacker.x said:
Your last setting is "Turn off backlight", I thought it would add an option to dim the screen to a lower backlight setting. Because I have the turn off backlight feature
Click to expand...
Click to collapse
The setting says that, but it doesn't actually turn it off. It just lowers it to 1 on a scale of 10 (I can still see my today screen). Tapping the screen or pressing a button lights it back up.
Hi!
I just got my new topas and I am wondering if there is a possibility to reduce the brightness of the screen when needed. As a biologist I often observe wildlife at night and look for a way to keep the screen so dim that I can just barely use it in the dark. This would help me keep my visibility down and my night vision up.
Is there any way to do this?
Best regards
Jamie White
Use this:
http://forum.xda-developers.com/showthread.php?t=548402
Hmm, doesn´t look too easy to use, but I´ll give it a try. Thanks for the quick reply!
The simplest way is to "turn the backlight off" which, with the Topaz, means a very dim backlight. You might find a small app to do that, for which you can put the shortcut in the start menu.
Alternatively, if the dimmest setting of the backlight when it's on is dim enough, you can make a shortcut to take you straight to the wm power settings page. I think the shortcut is: "20#ctlpnl cplmain.cpl,3" (without the "", just save the plain text file containing the characters as a yourname.lnk file and put it in \windows\start menu\programs folder.
Thanks Pete!
I just made the Lnk-file you suggested, but it´s still opened by word when I run it. I might have to make the file on my pc at home and see if that works out.
I think if I use a red and black desktop theme instead of the blue one I could do with the "backlight off" - option, although I have to try it out in the woods. I´m alway amazed how bright even a little light seems when you´ve been in the dark for some hours.
I just made the Lnk-file you suggested, but it´s still opened by word when I run it.
Click to expand...
Click to collapse
That's probably because WM file explorer is hiding the true extension (.txt), all you're doing is adding ".lnk" as part of the main filename. Get another file manager, I recommend Total Commander, which shows all files and their true extensions. It's even got a built in text editor, so you can modify and save your file without using Word.
The other thing I've realised since posting my reply, is some of the Control panel shortcuts don't work quite how they used to in previous versions of WM (although they won't do any harm if wrong).
I also came across this the other day http://forum.xda-developers.com/showthread.php?t=485141 which I haven't tried yet but sounds just what you're looking for.
I think this is a problem specific to the HD2 - basically, when i leave the phone on the auto backlight setting, it is too bright and therefore draining the battery. of course, setting it manually is a pain and it needs changing as conditions change etc.
What i am wonder is if there is any way of changing the auto so that it is consistently less bright? I have had a dig through the regedit but not really sure what i am looking for or doing!
I was guessing that there was a value that would be assigned to the brightness above the ambient brightness (from the light sensor) - can anyone enlighten me further?
Many thanks (and also for all those other posts i have used to help me make my phone exactly as i like it... CHT, BsB, Scilor etc!)
try Lumos.
nice. almost does too much! but good bit of software thus far. now to do some benchmarking... if only the sun would shine!
Controlling Backlight Settings
I took a different approach to resolve my problem -- keeping auto backlight turned off, but easily changing the backlight settings when I needed to change them. I created a shortcut called Backlight.lnk (that's a lowercase "L", not an "I" I discovered). I used a text editor and put in this line:
12#Powerexe.exe 2 - backlight tab
I saved it with the name Backlight.lnk and copied it to my Start/Programs folder using File Explorer. I moved the shortcut to the top of the Start menu where I can get to it quickly. I just tap Start and the shortcut icon and I am at the Backlight screen where I can quickly change the backlight level or the timeout settings. This saves a few taps compared with going in through the Settings screen.
I had tried Lumos and another program I found on the MS Marketplace, but both caused other problems for me.
PS: I found the line above in a posting at
http://forum.xda-developers.com/showthread.php?t=645916
It's an excellent tutorial on creating all kinds of shortcuts.
Try MVBKLight.
Very handy popup (plus a usefull torch).
I have both Auto and Manual controls. With links I immediately switch between sensor and the MVBKLight slider.
Try searching for autobacklight toggle. Basically, its an icon which when pressed on main screen enables disables autobacklight. So much better than lumos.
Please i would like your help for an issue i have about my proximity sensor on my U8800.
after the call,the screen turns off and then can not be open again.
you should remove the battery to do reboot.
I do not have problems with the official 2.3.5
because (I think) in the call settings there is a option for opening or closing the proximity sensor.
in the ics aurora version I have the sensor problem and i can not disable the proximity sensor.
And i should in any inbound or outbound calls to pull the battery off in order reboot and continue the phone operation.
I have already made some corrections, in the file sensors.default.so, witch switched the proximity sensor out of operation.
But in the same time the auto rotation of the screen stoped its operation.
How could you help me switch the proximity sensor out of opperation and make the auto rotation of the screen work.
http://www.easybytez.com/9ajn6e7t1akq
sorry my bad english.
any help??
happens tome sometimes too. Just hold power until it shoes then reboot
Sent from my u8800-51 running popura ICS
It would be hard to modify the sensors.default.so as it's compiled binary code. And simplest way to do it would be to rename the /dev/ entry; however that would also disable the light sensor.
I'd suggest you to do some code editing; I don't know whether the Phone.apk handles it or the frameworks, but if you decompile it you could find the code what is used to handle the proximity sensor and then just make it return 0 for example. But you should look up some tutorials on how to unpack it; how to understand smali code and so on.
Since I don't know if removing the permission does anything, check if you have /system/etc/permissions/android.hardware.sensor.proximity.xml . If you have it, remove it and reboot.
Or - try to search Google, you could find some information there.
the way about removing /system/etc/permissions/android.hardware.sensor.proximity.xml does not work!!!
Thanks i will try the other one!!
I think I found a way.. Open the sensors.default.so in HEX editor (Notepad++ may not do this properly); find /dev/proximity and modify it to /dev/proximitt for example (you can modify it to anything, just keep the same length. This way the proximity sensor info does not get reported to the Android.
Blefish said:
I think I found a way.. Open the sensors.default.so in HEX editor (Notepad++ may not do this properly); find /dev/proximity and modify it to /dev/proximitt for example (you can modify it to anything, just keep the same length. This way the proximity sensor info does not get reported to the Android.
Click to expand...
Click to collapse
Just tried the way with renaming the /dev/proximity to /dev/proximitt but nothing.
I have found several ways to fix it in the XDA developers, tried them but couln't do anything.
here modyfing file?
sorry my bad english.
I don't find any "ro.config.vc_call_vol_steps=......" or "...... music_vol_steps=....." settings in the A7 build.prop.
I added these lines to my build.prop to increase the steps from the default (which appears to be 7) to 30, but saw no change after reboot.
Is anyone aware of where the size of the volume steps is set, so I might make the steps smaller in adjustment?
Thanks
amphi66 said:
I don't find any "ro.config.vc_call_vol_steps=......" or "...... music_vol_steps=....." settings in the A7 build.prop.
I added these lines to my build.prop to increase the steps from the default (which appears to be 7) to 30, but saw no change after reboot.
Is anyone aware of where the size of the volume steps is set, so I might make the steps smaller in adjustment?
Thanks
Click to expand...
Click to collapse
Try and see if ro.config.media_vol_steps and ro.config.vc_call_steps works for you.
razorblader said:
Try and see if ro.config.media_vol_steps and ro.config.vc_call_steps works for you.
Click to expand...
Click to collapse
Tried it as you typed and also ro.config.vc_media_steps=30
but neither made a difference. I suspect it is set somewhere in the SystemUI where I don't have access.
Thanks
amphi66 said:
Tried it as you typed and also ro.config.vc_media_steps=30
but neither made a difference. I suspect it is set somewhere in the SystemUI where I don't have access.
Thanks
Click to expand...
Click to collapse
Thanks for the feedback, was gonna try this as well once I'll root my phone.
amphi66 said:
I don't find any "ro.config.vc_call_vol_steps=......" or "...... music_vol_steps=....." settings in the A7 build.prop.
I added these lines to my build.prop to increase the steps from the default (which appears to be 7) to 30, but saw no change after reboot.
Is anyone aware of where the size of the volume steps is set, so I might make the steps smaller in adjustment?
Thanks
Click to expand...
Click to collapse
If you want to, you can use gravity box to change it.
amphi66 said:
Tried it as you typed and also ro.config.vc_media_steps=30
but neither made a difference. I suspect it is set somewhere in the SystemUI where I don't have access.
Thanks
Click to expand...
Click to collapse
I've just tested this on B08 rooted and it works are you sure you've disabled system write protection so that your build.prop changes survive a reboot?
razorblader said:
I've just tested this on B08 rooted and it works are you sure you've disabled system write protection so that your build.prop changes survive a reboot?
Click to expand...
Click to collapse
I'm good there.
Thinking back tho, I only checked the ring tone steps from the home page (and that wasn't one of the volume adjustments made), so very like that build.prop edit DID work for what it was set for. I'll try again.
BTW, did you use the "media" or "music" entry?
amphi66 said:
I'm good there.
Thinking back tho, I only checked the ring tone steps from the home page (and that wasn't one of the volume adjustments made), so very like that build.prop edit DID work for what it was set for. I'll try again.
BTW, did you use the "media" or "music" entry?
Click to expand...
Click to collapse
'media' as the 'music' variant doesn't seem to work on newer iterations of Android any more.
ro.config.media_vol_steps=80
ro.config.vc_call_vol_steps=40
These settings work for me.
I just found this thread and I'd like to make this change on my phone too.
I find my phone has to go up to about 80% max volume before I can really hear things on the headphones/earbuds and at that point, it's only a couple clicks away from max volume.
I'm not very familiar with Android stuff yet, so could somebody provide me with some very basic step-by-steps on how to do this or where to find the file to change?
My phone is the US version, running B20 with locked BL but is rooted.
mozerxdaven said:
I just found this thread and I'd like to make this change on my phone too.
I find my phone has to go up to about 80% max volume before I can really hear things on the headphones/earbuds and at that point, it's only a couple clicks away from max volume.
I'm not very familiar with Android stuff yet, so could somebody provide me with some very basic step-by-steps on how to do this or where to find the file to change?
My phone is the US version, running B20 with locked BL but is rooted.
Click to expand...
Click to collapse
The suggestions in this thread only change the increments between volume steps, NOT overall volume. Good luck!
amphi66 said:
The suggestions in this thread only change the increments between volume steps, NOT overall volume. Good luck!
Click to expand...
Click to collapse
Yes, I understand this only changes the increments, but I would still like to find out how to make the change so I can have finer-grained control of the volume, even at higher levels.
mozerxdaven said:
Yes, I understand this only changes the increments, but I would still like to find out how to make the change so I can have finer-grained control of the volume, even at higher levels.
Click to expand...
Click to collapse
It's pretty straight forward since you are rooted: use a File Manager & Text Editor to add the lines below to /system/build.prop Save & then reboot. Your option as to the number of steps.
It is always good practice to make a nandroid backup prior to making changes to give you a recovery point in the event of a mistype or other error. Goodluck
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=30
amphi66 said:
It's pretty straight forward since you are rooted: use a File Manager & Text Editor to add the lines below to /system/build.prop Save & then reboot. Your option as to the number of steps.
It is always good practice to make a nandroid backup prior to making changes to give you a recovery point in the event of a mistype or other error. Goodluck
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=30
Click to expand...
Click to collapse
I did as suggested but it didn't seem to change anything for me.
I had to use the command to unlock system file changes first, because the change wasn't sticking after reboot at first.
I put those 2 lines at the bottom of the /system/build.prop file
Is it working properly on your phone?
Edit:: Scratch that, i was looking at the ringtone slider rather than the media/apps volume control.
Thank you!
mozerxdaven said:
I did as suggested but it didn't seem to change anything for me.
I had to use the command to unlock system file changes first, because the change wasn't sticking after reboot at first.
I put those 2 lines at the bottom of the /system/build.prop file
Is it working properly on your phone?
Edit:: Scratch that, i was looking at the ringtone slider rather than the media/apps volume control.
Thank you!
Click to expand...
Click to collapse
Yep, changing ringtone steps is tougher. It takes an edit of a System UI .jar file or the use of an Exposed Module.
Glad these worked for you!