Hi, after seeing that you have problems with auto brightness, I requested hw_config.sh and this one should fix the problems. One person reported auto brightness is disabled, other person reported that auto brightness became smoother.
1) Unzip
2) Push hw_config.sh to /system/etc
3) chmod 777 /system/etc/hw_config.sh
4) Reboot
Report the result.
Some further tweaks could be applied to completely disable auto-brightness if this isn't working. I'll just need some volunteers.
Best regards
I would like to try, but I don't want to mess around too much.
So my questions are:
1. Is there a way to revert if something is not right? (Other than re-flash the whole thing)
2. Can you clearly say whether it disables auto-brightness or enables it? (I can't find any open under the brightness for "auto". So I wonder why we have sensor for this?)
Related
Here is a couple of scripts of everyone, this will make your roms ANYROM for the eris turn on or off your trackball lights, and or softkey lights
I noticed a few roms that have problems with lights so I figured I would put these here to fix this problem.
If you just want to be able to turn on or off your softkey lights or trackball just download the script and put then in /sdcard/gscript
now download gscript app from the market and load a script file from sdcard
save the script and run threw gscript.
http://www.multiupload.com/1EWEV8MK48
If your a rom developer you can easily make these changes to the init.post-boot.sh and have the settings started at boot just add what ever script you want to init.post-boot.sh like this
open init.post-boot.sh add to file at the very top second line
Code:
# Initialize lights at boot to enable softkey lights noti$
echo 1 > sys/class/leds/vtkey-backlight/brightness
sleep 1
save and reboot.
So, to be clear, these scripts switch on or off the softkey lights and only switch on the trackball light, right? They do not enable or turn on the ability of the ROM to control these, right? For that you would have to incorporate some system components (or a 3rd-party app like Light Flow, which seems to be able to do the same thing). I'm not trying to give a hard time, just trying to understand how this works. I've tried doing similar things on evervolv and GST with no luck.
Oh, and one other thing, in your readme you mention
Notice, if you make trackball on run at boot your phone will lag, and after a while reboot this is a known issue to do with memory loss. Just run from gscript and you will be ok, it doesnt do anything to memory, just uses up all the ram/buffer so your phone reboots. if run at startup if it is just run through gscript everything will work fine.
Click to expand...
Click to collapse
What is the "known issue to do with memory loss?" I'm working on a navigation-related reboot problem at the moment and wondering about the ROM using up the RAM/buffer and if it is related. Mil gracias!
klobkelosh said:
So, to be clear, these scripts switch on or off the softkey lights and only switch on the trackball light, right? They do not enable or turn on the ability of the ROM to control these, right? For that you would have to incorporate some system components (or a 3rd-party app like Light Flow, which seems to be able to do the same thing). I'm not trying to give a hard time, just trying to understand how this works. I've tried doing similar things on evervolv and GST with no luck.
Click to expand...
Click to collapse
the lights on works but need to find out how to make them go off,, i add them to the rom but lights jjust stay on even with the phone sleeping , i sent a pm just waitin on a answer
Ok, you can use Light Flow from the market to control the lights but yes, this is only to enable and disable the light. for some reason roms are haveing a problem turning on the lights there just doesnt seem to be any one or off switch. I also have found that in alot of the roms a few that i have flashed that have been ported from the hero are missing a few of these lines
chown system system /sys/class/leds/vtkey-backlight/brightness
chown system system /sys/class/leds/amber/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/green/brightness
Click to expand...
Click to collapse
and few others like trigger,uevent if you want the full list ill pm it
androidifyme said:
Ok, you can use Light Flow from the market to control the lights but yes, this is only to enable and disable the light. for some reason roms are haveing a problem turning on the lights there just doesnt seem to be any one or off switch. I also have found that in alot of the roms a few that i have flashed that have been ported from the hero are missing a few of these lines
and few others like trigger,uevent if you want the full list ill pm it
Click to expand...
Click to collapse
im looking in my boot img and i see all those lines u mentioned
pming.....
ok ,, and btw i linked them to ur thread in the op
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
thejrcrafter2 said:
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
Click to expand...
Click to collapse
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
leapinlar said:
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
Click to expand...
Click to collapse
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
thejrcrafter2 said:
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
Click to expand...
Click to collapse
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
leapinlar said:
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Had the same problem on my Nook HD running CM10.1 on the hybrid install and this fixed it today. My issue was that I think I clicked "auto" while adjusting on the slider and then the brightness was stuck and the "auto" was not checked nor was it selectable. Flipped the bit from 1 to 0 and now it's working ok. Doing a CWM backup now so I'll have the fix in my gold install.
Had this problem on my Samsung T679. Just fixed it and figured I'd record the steps for my own and other's reference. I'm cheap and like doing things the hard way, so I didn't spring for SQLiteEditor. I found that sqlite3 was already installed on the phone.
Before starting: use cwm to make backup, just in case.
1. Force-stop Settings app.
2. Get /data mounted read-write.
3. Open a shell (recommend via ssh/adb, because we have some typing to do).
4. cd /data/data/com.android.providers.settings/databases
5. rm settings.db-shm settings.db-wal (not sure about this step, but the change didn't seem to stick otherwise.)
6. sqlite3 settings.db
Here is my session, you should get the idea:
Code:
sqlite> .tables
android_metadata bookmarks system
bluetooth_devices secure
sqlite> select * from system
...> where name like "%bright%";
71|status_bar_brightness_control|1
278|screen_brightness_mode|1
605|expanded_brightness_mode|0OV=I=XseparatorX=I=VO1OV=I=XseparatorX=I=VO3OV=I=XseparatorX=I=VO5
607|screen_brightness|30
sqlite> update system
...> set value=0
...> where _id=278;
sqlite> .quit
screen_brightness_mode needs to be changed to 0. Don't forget the semi-colons. Now fire up the Settings app and you should be able to enable the status-bar swipe brightness control. I had to toggle it once before it worked.
Hi
I'm trying to find a way to automate a process of turning on and off High Sensitivity Mode on i9505 with rooted stock 4.3.
What i'm trying to do is to get temperature from builtin temp sensor and then enable or disable that mode.
I found that Tasker has option to get temperature status from sensor now i need to select that checkbos in display settings somehow.
Does anybody knows how can i acomplish that??? i mean how can i make tasker enable High Sensitivity Mode (increase touch sensitivity in display settings)???
error post
anyone???
or maybe anyone knows how to enable high sensitivity mode from terminal or maybe some other way???
Found it
It's actually rather simple, turns out.
You need to use the secured settings app (separate install).
The set up an action for:
Secured Settings->Custom ROM->Samsung->Touch sensitivity (enable/disable).
Enjoy
I've seen a few posts about over-sensitive auto rotate and experienced the same myself. After a bit of digging I found this post on reddit. It's seems a bit out of date for the current version of Tasker but you should make it past the differences just fine. This method was not created by me and I take no credit or responsibility:
Originally posted by kindall on Reddit:
Requires:
Tasker (of course)
A ROM that lets you choose what orientations your phone's display can auto-rotate into. I use Carbon, where this is under Settings > Display > Rotation. In other ROMs it may be in a different place. If you have a stock ROM you may or may not have such a feature at all.
Steps:
1) Go into your phone's orientation settings and TURN OFF everything but 90 degrees. Don't worry, the phone will still display in portrait mode; you just have to turn automatic rotation off! In fact, that's how this trick works: we'll use Tasker to turn auto-rotate on and off as a way to force the phone to be in either portrait or landscape.
2) At the bottom of Tasker > Preferences > Monitor, make sure Orientation State Accuracy is set to High. BTW, if you don't see these settings, make sure Beginner Mode (in the UI tab of the Tasker prefs) is not set.
3) Now create a profile: Name: Landscape; Contexts: [State: Display On; State: Orientation Left Side]. Create a new Enter task containing one action: Display Rotation On.
4) Create a second profile: Name: Portrait; Contexts: [State: Display On; State: Orientation Standing Up]. Create a new Enter task containing one action: Display Rotation Off.
5) Set the Restore Settings checkbox in both of these profiles to Off. (Long-press the profile name, then click the settings icon in the toolbar at the top of the screen.) Otherwise Tasker will switch the setting back as soon as the phone is no longer in the exact position needed to activate the profile, which will defeat the purpose.
Optionally:
6) add a profile that turns Display Rotation Off at startup, and perhaps another one that turns Display Rotation Off when the display is turned off, if you want to force portrait mode at either of these occasions.
Now your phone won't auto-rotate into landscape until you hold it pretty much exactly in landscape orientation, and won't rotate back until you hold it pretty much exactly in portrait orientation. You can control the required accuracy using the Orientation State Accuracy setting in Tasker, mentioned in step 2.
If you want to, you can add a third profile for rotating to the other landscape mode, and activate 270 degrees in your ROM's display rotation preferences. While the phone will freely rotate the display between these orientations when auto-rotation is on, it should be difficult to switch accidentally since they are physically so far apart.
So as the lowest screen brightness of our beloved Pixel C is just a little above the light of a thousand suns, I researched how it can be lowered.
But mind that you WILL NEED ROOT for this to work. Also mind that I'm not responsible if you **** up your device.
1. Root your device
2. Install any Terminal that can work with the root OR use adb
3. Switch to root user ("su root" OR "adb root")
4. Execute this "echo 3 > /sys/class/backlight/lpm102a188a-backlight/brightness"
5. Profit!
Instead of the "3" in that command you can use any value from 1 to 255.
BUT I strongly recommend NOT to set the brightness to 1 because your backlight will turn off.
Also on value 2 my display flickers so I would be careful with this.
Have fun without bleeding eyes!
Adaptive brightness
Termynat0r said:
So as the lowest screen brightness of our beloved Pixel C is just a little above the light of a thousand suns, I researched how it can be lowered.
But mind that you WILL NEED ROOT for this to work. Also mind that I'm not responsible if you **** up your device.
1. Root your device
2. Install any Terminal that can work with the root OR use adb
3. Switch to root user ("su root" OR "adb root")
4. Execute this "echo 3 > /sys/class/backlight/lpm102a188a-backlight/brightness"
5. Profit!
Instead of the "3" in that command you can use any value from 1 to 255.
BUT I strongly recommend NOT to set the brightness to 1 because your backlight will turn off.
Also on value 2 my display flickers so I would be careful with this.
Have fun without bleeding eyes!
Click to expand...
Click to collapse
Thanks. Do you happen to know if there's something like a "step size" setting for Adaptive Brightness? In low light, mine goes from a little too bright to too dim.
eecummings said:
Thanks. Do you happen to know if there's something like a "step size" setting for Adaptive Brightness? In low light, mine goes from a little too bright to too dim.
Click to expand...
Click to collapse
No, sorry. But maybe it's somewhere around this file.
Termynat0r said:
So as the lowest screen brightness of our beloved Pixel C is just a little above the light of a thousand suns, I researched how it can be lowered.
But mind that you WILL NEED ROOT for this to work. Also mind that I'm not responsible if you **** up your device.
1. Root your device
2. Install any Terminal that can work with the root OR use adb
3. Switch to root user ("su root" OR "adb root")
4. Execute this "echo 3 > /sys/class/backlight/lpm102a188a-backlight/brightness"
5. Profit!
Instead of the "3" in that command you can use any value from 1 to 255.
BUT I strongly recommend NOT to set the brightness to 1 because your backlight will turn off.
Also on value 2 my display flickers so I would be careful with this.
Have fun without bleeding eyes!
Click to expand...
Click to collapse
Will this stay after dirty flashing update or it has to be redone ?
lapocompris said:
Will this stay after dirty flashing update or it has to be redone ?
Click to expand...
Click to collapse
I will stay just for a few minutes to hours, depending when android wants do change the brightness again.
EDIT: So no
https://play.google.com/store/apps/details?id=mobi.pruss.superdim&hl=en_GB might do the same thing for you guys. As far as I know it's just a wrapper around this sort of command.
There is a "settings" command to adjust the adaptive brightness value. I haven't tried this, but the following terminal command might work:
settings put system screen_auto_brightness_adj (value between -0.5 and +0.5)
Root is needed, of course. I found this in a tasker thread on reddit: Edit: I cannot add links yet. Search for "reddit tasker how to replace some secure settings actions"
Anyway to make this permanent? Every time I switch off and on the screen, it becomes brighter again. Thanks
Testes with Xiaomi Mi9 use this command:
echo 3 > /sys/class/backlight/backlight/brightness