Database Users

[INFO] Auto-Backlight Settings for Cyanogenmod ROMs

Some of you would already know that the lightsensor filter in the Evo kernels is now working ( I would say atleast 80% working ) and responds best to Desire builds.
I have it working just fine for the last few hours on the AndroidMedaUltimate 1.3 version. Here are my settings in case you wanna try out.
CAUTION : If you change the values too many times, lightsensor stops responding and you will not see any changes in values. I believe thats CM related.
My Setup
Build : AndroidMedaUltimate 1.3
Kernel : StockEvo Autobuild dated Oct 29
(No SetCpU/taskkillers/etc)
1. Make sure Auto Brightness is disabled under Settings->Display
2. Goto Settings->Cyanogenmod Settings->User Interface->Automatic Backlight
3. Under Light Sensor filter, make sure Enabled is unchecked (No filters!)
4. Under Light levels, check "Allow Light Decrease" and set "Decrease hysteresis" to 0% (Yes thats no typo, for some reason sensor responds faster this way )
5. Check "Use Custom"
6. Tap on Edit Other Levels...
7. Now set values as in below screenshot and table
Lower ....... Upper ............Screen...........Buttons
0 ____________ 169 _______________ 85 _____________ 255
170 __________ 279 _______________ 120 ____________ 255
280 __________ 749 _______________ 170 ____________ 255
800 __________ () _______________ 254 ____________ 255
Note - The last value is 254, for some reason when I had it as 255 and went outside, brightness got stuck at max and sensor stopped responding
Click to expand...
Click to collapse
8. Tap Save & Apply
9. Wait for few seconds and try covering and changing light, you should see the sensor values change on top
10. Once that starts happening, enable Auto Brightness under Display settings
11. Reboot (Best Practice )
---------------
You can add more levels and adjust the lower/upper range alongwith the Screen values (30-255) to suit you better. However, the more you change it the more its likely to end up not working. Dont know why.

Interesting, will be testing this today with Shubcraft 2.0 and post my findings.

thanks, done the changes and testing with Htcclays V1.4.
edit: it is working very well for me.no lightsensor issue for me.
many thanks for your tip.

Thank you works grat

v-b-n said:
1. Make sure Auto Brightness is disabled under Settings->Display
2. Goto Settings->Cyanogenmod Settings->User Interface->Automatic Backlight
3. Under Light Sensor filter, make sure Enabled is unchecked (No filters!)
4. Under Light levels, check "Allow Light Decrease" and set "Decrease hysteresis" to 0% (Yes thats no typo, for some reason sensor responds faster this way )
5. Check "Use Custom"
6. Tap on Edit Other Levels...
7. Now set values as in below screenshot and table
8. Tap Save & Apply
9. Wait for few seconds and try covering and changing light, you should see the sensor values change on top
10. Once that starts happening, enable Auto Brightness under Display settings
11. Reboot (Best Practice )
---------------
You can add more levels and adjust the lower/upper range alongwith the Screen values (30-255) to suit you better. However, the more you change it the more its likely to end up not working. Dont know why.
Click to expand...
Click to collapse
Thanks very much for this, a few questions if you please.....
I'm using Typhoon 3.8.0.
I'm finding these settings under
Settings->Cyanogenmod Settings->Display->Automatic Backlight
not
Settings->Cyanogenmod Settings->User Interface->Automatic Backlight
And I don't know if that has any underlying significance - like it not being implemented in the same way in Typhoon?
Secondly you don't mention the "screen dim level" setting I see in the same "Display" menu. I've wound it down to 6 (default is 20), but not seeing much difference?
Thirdly, I've used the settings in the "other levels" as your table shows, but I wonder why you used those settings, what drove you to pick those numbers?
Finally, you talk about changing it too much stopping it working....when that happens what do you do to revert? Reboot? Or return to defaults and reboot? or something else?
Thanks, I'm hoping this will help balance out the fact that up to now I've not used auto-brightness so as to keep the battery life up but it's a bit of a pain in bright light to see the screen....
Thanks

[GUIDE] to Ezekeel's Touch Wake / Backlight Dimmers

#!/system/bin/sh
#
#
#
# DimmerMod Guide
#
# All credit for this mod goes to Ezekeel, who created it,
# and to the kernel devs (e.g. morfic, reddv1, and
# mathkid95) who have implemented it. If you're not
# rooted and using a kernel that supports it, such as
# Trinity, Lucid Nexus, or Matrix, don't ask why it
# doesn't work. If you don't know what I'm talking
# about, this might not be for you.
# Lines not preceded by a pound are commands that
# may be entered in terminal emulator. If you get a
# "directory nonexistent" error, your kernel does not
# support this. If you're familiar with init.d scripts, you
# know what to do.
#
#
#
# Screen Dimmer
# Screen dimmer will turn the screen off at the
# specified interval. Touching the screen will turn it
# back on. It does not play nicely with movies or other
# things that should keep the screen awake, but does
# allow the system and running apps to continue
# running, which shortens battery life. It has been
# made obsolete by touch wake dimmer. Use that
# instead.
#
# Enable:
echo 1 > /sys/class/misc/screendimmer/enabled
#
# Disable:
echo 0 > /sys/class/misc/screendimmer/enabled
#
# Set screen time-out delay,
# in milliseconds (example: 25 seconds). Value of 0 =
# indefinite delay (not useful for screen dimmer).
echo 25000 > /sys/class/misc/screendimmer/delay
#
#
#
# Touchkey Backlight Dimmer
# Touchkey backlight dimmer turns off the softkey
# backlight at the specified interval. It will turn back
# on (temporarily) when you touch the menu buttons.
# The battery savings are negligible. It is more of a
# user experience tweak. Some people prefer the way
# the phone looks with them off, particularly when
# watching movies. It can also be useful for bln users,
# who may prefer the keys to light up only when there
# is a notification.
#
# Disable:
echo 0 > /sys/class/misc/backlightdimmer/enabled
#
# Enable:
echo 1 > /sys/class/misc/backlightdimmer/enabled
#
# Set backlight dimmer time-out delay,
# in milliseconds (example: 3 seconds). Value of 0 =
# indefinite delay (not useful for backlight dimmer).
echo 3000 > /sys/class/misc/backlightdimmer/delay
#
#
#
# Touch Wake
# Touch wake will keep the touch input and menu
# softkeys active for the specified delay. The screen
# timeout will work normally, but you can then wake
# the phone by touching the screen or menu buttons
# instead of the power button. If you press the power
# button (or the touch wake expires) the phone will
# then be woken only by the power button, like normal.
# If you're running CyanogenMod, you can prevent the
# lockscreen from displaying when using touch-to-wake.
# Just set CyanogenMod settings->Lockscreen->Delay
# and timeout->Screen timeout delay to the same
# interval as touchwake/delay.
#
# Disable:
echo 0 > /sys/class/misc/touchwake/enabled
#
# Enable:
echo 1 > /sys/class/misc/touchwake/enabled
#
# Set touch wake time-out delay,
# in milliseconds (example: 5 minutes). Value of 0 =
# indefinite delay (If you do this, touch wake will stay
# active indefinitely. Press the power button to disable
# it when you put the phone in your pocket.)
echo 300000 > /sys/class/misc/touchwake/delay
#
#
#
# This guide brought to you by Maximilian Mary.

If you're on the xda app, this reads better with the phone sideways.

Maximilian Mary said:
#!/system/bin/sh
#
#
#
# DimmerMod Guide
#
# All credit for this mod goes to Ezekeel, who created it,
# and to the kernel devs (e.g. morfic & reddv1) who
# have implemented it. If you're not rooted and using
# a kernel that supports it, such as Trinity or Lucid
# Nexus, don't ask why it doesn't work. If you don't
# know what I'm talking about, this might not be for
# you.
# Lines not preceded by a pound are commands that
# may be entered in terminal emulator. If you get a
# "directory nonexistent" error, your kernel does not
# support this. If you're familiar with init.d scripts, you
# know what to do.
#
#
#
# Screen Dimmer
# Screen dimmer will turn the screen off at the
# specified interval. Touching the screen will turn it
# back on. It does not play nicely with movies or other
# things that should keep the screen awake, but does
# allow the system and running apps to continue
# running, which shortens battery life. It has been
# made obsolete by touch wake dimmer. Use that
# instead.
#
# Enable:
echo 1 > /sys/class/misc/screendimmer/enabled
#
# Disable:
echo 0 > /sys/class/misc/screendimmer/enabled
#
# Set screen time-out delay,
# in milliseconds (example: 25 seconds). Value of 0 =
# indefinite delay (not useful for screen dimmer).
echo 25000 > /sys/class/misc/screendimmer/delay
#
#
#
# Touchkey Backlight Dimmer
# Touchkey backlight dimmer turns off the softkey
# backlight at the specified interval. It will turn back
# on (temporarily) when you touch the menu buttons.
# The battery savings are negligible. It is more of a
# user experience tweak. Some people prefer the way
# the phone looks with them off, particularly when
# watching movies. It can also be useful for bln users,
# who may prefer the keys to light up only when there
# is a notification.
#
# Disable:
echo 0 > /sys/class/misc/backlightdimmer/enabled
#
# Enable:
echo 1 > /sys/class/misc/backlightdimmer/enabled
#
# Set backlight dimmer time-out delay,
# in milliseconds (example: 3 seconds). Value of 0 =
# indefinite delay (not useful for backlight dimmer).
echo 3000 > /sys/class/misc/backlightdimmer/delay
#
#
#
# Touch Wake
# Touch wake will keep the touch input and menu
# softkeys active for the specified delay. The screen
# timeout will work normally, but you can then wake
# the phone by touching the screen or menu buttons
# instead of the power button. If you press the power
# button (or the touch wake expires) the phone will
# then be woken only by the power button, like normal.
# If you're running CyanogenMod, you can prevent the
# lockscreen from displaying when using touch-to-wake.
# Just set CyanogenMod settings->Lockscreen->Delay
# and timeout->Screen timeout delay to the same
# interval as touchwake/delay.
#
# Disable:
echo 0 > /sys/class/misc/touchwake/enabled
#
# Enable:
echo 1 > /sys/class/misc/touchwake/enabled
#
# Set touch wake time-out delay,
# in milliseconds (example: 5 minutes). Value of 0 =
# indefinite delay (If you do this, touch wake will stay
# active indefinitely. Press the power button to disable
# it when you put the phone in your pocket.)
echo 300000 > /sys/class/misc/touchwake/delay
#
#
#
# This guide brought to you by Maximilian Mary.
Click to expand...
Click to collapse
thanks! now i have something to link for people instead of having to type it out every time some asks

Korean Version
Hello~
Thanks for the great guide.
I've translated the guide into Korean for my fellow countrymen.
http://caleb1783.tistory.com/200
Hope you dont mind~!
Cheers,

anyone able to make Widgetlocker play nice with Touch Wake?
After screen timeout, Widgetlocker kicks in immediately.

Sorry for the newbie question, but what should the init.d file be named? I guess you can name it whatever you want but there has to be a specific number at the begining. What should that number be?

Sorry if this is a stupid question, but how do I get the Touch key dimmer to stick after reboot?

MistaJae said:
Sorry if this is a stupid question, but how do I get the Touch key dimmer to stick after reboot?
Click to expand...
Click to collapse
Go to the market and download an app called Script Manager and use the script I've attached to this post, it activates the touchkey back light dimmer after 30 seconds and can be easily modified to whatever you like. I found the script somewhere on the board but one can be easily created with Script Manager so that you can take advantage of Ezekeel's mods and not have to worry about setting them everytime you reboot.
Touchkey Backlight Dimmer script: http://db.tt/y0IHXZCA

onigiri1692 said:
Go to the market and download an app called Script Manager and use the script I've attached to this post, it activates the touchkey back light dimmer after 30 seconds and can be easily modified to whatever you like. I found the script somewhere on the board but one can be easily created with Script Manager so that you can take advantage of Ezekeel's mods and not have to worry about setting them everytime you reboot.
Touchkey Backlight Dimmer script: http://db.tt/y0IHXZCA
Click to expand...
Click to collapse
Just what I was after. I have changed the timeout to 3 secs instead of 30.
Many thanks!

Uh with the zero delay of backlight dimmer, it loses the functionality of holding home button. Can't switch apps :/ But 1 sec is ok.

onigiri1692 said:
Go to the market and download an app called Script Manager and use the script I've attached to this post, it activates the touchkey back light dimmer after 30 seconds and can be easily modified to whatever you like. I found the script somewhere on the board but one can be easily created with Script Manager so that you can take advantage of Ezekeel's mods and not have to worry about setting them everytime you reboot.
Touchkey Backlight Dimmer script: http://db.tt/y0IHXZCA
Click to expand...
Click to collapse
Getting a sytax error when running this in script manager. I tried zipped as is and unzipped as well. Wondering if I missed a step or something.

wild1z said:
Getting a sytax error when running this in script manager. I tried zipped as is and unzipped as well. Wondering if I missed a step or something.
Click to expand...
Click to collapse
You want to run the file that is inside the script. The only thing I can think of is maybe you aren't running the script as root.

onigiri1692 said:
You want to run the file that is inside the script. The only thing I can think of is maybe you aren't running the script as root.
Click to expand...
Click to collapse
Ok, so I unzipped it on my computer. Then copied the file to the phone. Then ran script manager as root and to run on start up. This time it ran with no errors and it worked. Thank you so much for the reply. This opens up some doors for me. Thanks button pushed.

it didn't work on my Nexus S with script manager
i write it , and select as root and at boot
but after i reboot , just like it didn't run this script , touchwake didn't work
------------
this is what i have on my script file
#!/system/bin/sh
echo 1 > /sys/class/misc/touchwake/enabled
echo 10000 > /sys/class/misc/touchwake/delay
echo 1 > /sys/class/misc/deepidle/enabled
Click to expand...
Click to collapse
something wrong ?
problem solved , thanks , although i don't even what have i done to solve it ... - - !!!

qtwrk said:
it didn't work on my Nexus S with script manager
i write it , and select as root and at boot
but after i reboot , just like it didn't run this script , touchwake didn't work
------------
this is what i have on my script file
something wrong ?
problem solved , thanks , although i don't even what have i done to solve it ... - - !!!
Click to expand...
Click to collapse
Go into the SU app next time and make sure The Script Manager is enabled. Happened to me too. Cheers.

I have created an application to make this thing easier
go to this thread
http://forum.xda-developers.com/showthread.php?t=1333696
thanks

[Hack]Improved Hardware Auto Brightness

This is a hacky fix but it is a fix.
It gives you a backlight that will go from dim to full bright without the need for any other apps running. It's not uber configurable like dedicated apps as it's limited by hardware but it requires 0 ram, 0 runtime and 0 battery
Append the following to hw_config.sh. The sleep is a hack but a viable one - hw_config is fired up by one of the rc files as a oneshot service so it should be OK to extend it's operation
If you prefer you could just make a standalone script with everything after the sleep command (make sure you have the dev= assignment from hw_setup too!) and fire it off with a script executer of your choice
Code:
#this sleep ensures that the system is up and done [email protected] with light levels before setup
sleep 30
#select als group for backlight
echo 1 > $dev/leds/lcd-backlight1/als_group
echo 1 > $dev/leds/lcd-backlight2/als_group
#set both to max. brightness - als will lower
echo 255 > $dev/leds/lcd-backlight1/brightness
echo 255 > $dev/leds/lcd-backlight2/brightness
#set custom als curve
echo 7,1,48,72,24,255,0 > $dev/als_group1
#set custom filter frequency
echo 1000 > $dev/als_filter_down_speed_mHz
echo 1000 > $dev/als_filter_up_speed_mHz
#turn on hardware als
echo 1 > $dev/als_on
Notes
Make sure you have completely uninstalled any other light controllers - Velis in particular wreaks havoc even when disabled - it still receives the screen on intent and resets the brightness which results in a black display - guess how I know ....
Make sure you have disabled auto brightness control in the standard Sony settings and set the slider to full bright for good measure
I use nobootanimation so my phone boots a bit quicker than some. It might be that sleep 30 isn't long enough for an animated startup
Best thing is probably to create a setup script and run that to satisfy yourself the hack works. Then add it to hw_config and increase the delay if it doesn't work!
If you want to know more about the als setup check HERE or read the AS3677 datasheet.
Sadly I wasn't able to find out how the ALS curves are loaded into the current system, hence the direct hardware poking
There's some useful debug capability built into the sysfs
cat $dev/debug to see light sensor outputs and calculated backlight settings
cat als_group1 to read back the curve settings complete with a graph showing the response curve
A software guy could probably easily make an apk that hooked to the SCREEN_ON intent to program all this (and have a nice gui to show/edit the curve) but I'm a hardware engineer so that ain't me!

It's easier to just use Lux. Thanks anyway.

pakatsui said:
It's easier to just use Lux. Thanks anyway.
Click to expand...
Click to collapse
LUX, YAB or other brightness app will don`t work correct on all my Xperias. Only with "system brightness settings" active in the background this apps will change the brightness in realtime. When i close the systemsettings brightness will change no longer or with some luck once when unlocking.
so i will test this Hack, hope it helps to become a wide range in realtime.

heross said:
LUX, YAB or other brightness app will don`t work correct on all my Xperias. Only with "system brightness settings" active in the background this apps will change the brightness in realtime. When i close the systemsettings brightness will change no longer or with some luck once when unlocking.
so i will test this Hack, hope it helps to become a wide range in realtime.
Click to expand...
Click to collapse
Lux works fine. I'm using it now.
Sent from my Xperia SP using xda premium

Hello t_o_f,
today i have made test this fix in Car navigation from sunlight to the moon. awesome. this is the best fix i have always seen for xperia autobrightness. :good::laugh::good: ten points from germany.
the best, lowest brightness it is configurable with the Stock slider!

Call me daft. I disabled auto brightness, jacked the brightness to high, and have no other brightness apps installed. I appended the above to /etc/hw_config.sh and rebooted.
auto brightness didn't work. It was still jacked up to high so I enabled it and tested, still not working. Did I do something wrong? I'm on 254 rooted.

Possible Fix For Touchscreen Issues/Misses (Updated 08/29)

SEE UPDATE BELOW
After doing some more digging on surfaceflinger, atd, and their related libs, I found some interesting entries in a "strings" analysis of libinputflinger.so. Loads of stuff on touch calibration. I noticed some repeated strings that looked like they're assigned to different properties. You can see this clearly by entering:
Code:
strings /system/lib/libinputflinger.so | grep -iE '(^touch\.|[ ][ ]touch\.)'| sed -e 's/^[ \t]*//' | sort -n | uniq
The terminal returns
Code:
touch.coverage.calibration
touch.coverage.calibration: box
touch.coverage.calibration: none
touch.deviceType
touch.distance.calibration
touch.distance.calibration: none
touch.distance.calibration: scaled
touch.distance.scale
touch.distance.scale: %0.3f
touch.gestureMode
touch.orientation.calibration
touch.orientation.calibration: interpolated
touch.orientation.calibration: none
touch.orientation.calibration: vector
touch.orientationAware
touch.pressure.calibration
touch.pressure.calibration: amplitude
touch.pressure.calibration: none
touch.pressure.calibration: physical
touch.pressure.scale
touch.pressure.scale: %0.3f
touch.size.bias
touch.size.bias: %0.3f
touch.size.calibration
touch.size.calibration: area
touch.size.calibration: box
touch.size.calibration: diameter
touch.size.calibration: geometric
touch.size.calibration: none
touch.size.isSummed
touch.size.isSummed: %s
touch.size.scale
touch.size.scale: %0.3f
touch.wake
I looked up some of strings on the net, and lo and behold, they're build.prop entries! You can see the props above that have different strings to assign to them. The ones with a "%0.3f" refer to a number value, and the one with "%s" is a boolean 0/1.
I've only done a little testing, but I found a baseline of improvement values to make our touch screens more responsive. Some of the properties I couldn't find info on, so I'm testing some values like touch.distance.scale. I feel like I have definitely noticed improvements though. I'm no longer so pissed off using my phone, and the frequency of misses overall seems significantly lower. It's acceptable now. Here's what I'm using now at the end of my build.prop:
Code:
##### touch ######
touch.deviceType=touchScreen
# (geometric, diameter, box, area)
touch.size.calibration=geometric
touch.size.scale=100
# (amplitude, physical, none)
touch.pressure.calibration=amplitude
touch.pressure.scale=0.1
touch.gestureMode=pointer
# (interpolated, vector, none)
touch.orientation.calibration=interpolated
# (box, none)
touch.coverage.calibration=box
For detailed information on these touch properties, read here(search for the property you're interested in; the page is pretty long). Some are self-explanatory and others we'll just need to test more. Check them out and see if any calibration values make a significant change. Just copy the above code and paste to the bottom of /system/build.prop with a nice file manager like Solid Explorer. Warning: Adding these entries in the build.prop will change the default touch properties. You can always change them back to stock by removing or commenting the entries from build.prop. I assume most values are aafe, but I can't be sure.
Also worth noting. I found some additional build.prop values to make Android snappier. The fling/swipe velocity make a big difference. Not sure what the others correlate to.
Code:
##### touch related #####
view.touch_slop=2
view.scroll_friction=1.5
view.minimum_fling_velocity=25
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.min_pointer_dur=8
windowsmgr.max_events_per_sec=200
EDIT: For detailed information on these touch properties, read here.
I'm gonna add some "profiles" of touch settings to use down here.
This one is for a Nexus 4 I believe. I'm trying it out now, and it seems pretty good. My goal is to emulate the touch experience I had with that phone.
Code:
##### touch ######
touch.deviceType=touchScreen
touch.orientationAware=1
# (geometric, diameter, box, area)
touch.size.calibration=diameter
touch.size.scale=10
touch.size.bias=0
touch.size.isSummed=0
# (amplitude, physical, none)
touch.pressure.calibration=amplitude
touch.pressure.scale=0.005
touch.gestureMode=pointer
# (interpolated, vector, none)
touch.orientation.calibration=none
UPDATE
Hey guys, so here's an update to what I've found out about the touch screen and its issues. I apologize for my low activity on xda. I've been real busy working on some linux projects.
First, in order for the touch.* settings to work, they need to be put in an .idc (input device configuration) file with the name of the device. For the G4, that is: /system/usr/idc/touch_dev.idc.
If you have another phone or want to check, you can get the name of your touch screen device with the terminal command:
Code:
for i in /dev/input/event*; do j="$(getevent -i $i | grep -i touch)"; j=${j#*name: }; [[ -z $j ]] || echo ${j//\"/}; done
Before you go try out the .idc file, I want to warn you that certain settings will disable the touch screen. If this happens, you'll need to use adb to delete or move /system/usr/idc/touch_dev.idc somewhere else so that it doesn't get loaded when the phone boots. These are some settings you must NOT change in the .idc file:
Code:
touch.deviceType = touchScreen
touch.coverage.calibration = box
These are the settings I'm currently using:
Code:
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.size.calibration = diameter
touch.size.scale = 1
touch.size.bias = 0
touch.size.isSummed = 0
touch.pressure.calibration = physical
touch.pressure.scale = 0.001
touch.orientation.calibration = none
touch.distance.calibration = none
touch.distance.scale = 0
touch.coverage.calibration = box
touch.gestureMode = spots
MultitouchSettleInterval = 1ms
MultitouchMinDistance = 1px
TapInterval = 1ms
TapSlop = 1px
I'm not sure if the Multitouch* and Tap* settings work or if adding more values from libinputflinger will work. There's little documentation on using settings that don't begin with "touch." You might have to do some experimentation and try other entries in the "strings /system/lib/libinputflinger.so" readout. I would also try using the first settings I posted if these don't seem to help.
Another thing I found out is that this phone performs better with low entropy. You can monitor your current entropy level in the terminal:
Code:
watch "cat /proc/sys/kernel/random/entropy_avail"
It's usually around 2000+ and peaks at 4096 with high activity which is where I think lag comes in. I found that lowering it to under 1000 average cut out the lag spikes I was getting:
Code:
echo 16 > /proc/sys/kernel/random/read_wakeup_threshold
echo 16 > /proc/sys/kernel/random/write_wakeup_threshold
I went ahead and added that to an init.d script. This doesn't have any side effects I've noticed besides possible increased battery life, since the "hwrng" process that generates entropy has no work to do. In case you don't have init.d, make sure busybox is installed, run this command in the terminal, and you'll have init.d startup:
Code:
mount -o remount,rw /system; echo "sleep 300 && run-parts /system/etc/init.d" >> /system/etc/init.qcom.post_boot.sh; mount -o remount,ro /system
One last thing to mention. The touch device has a little section in sysfs under: /sys/devices/virtual/input/lge_touch. There's some interesting information you can find there, values you can change, and tests you can run. Any file with a name ending in "test" can be run by opening the file, yes sysfs files are weird like this. All tests pass for me except "abs_test":
Code:
cat /sys/devices/virtual/input/lge_touch/abs_test
> ========RESULT=======
> Absolute Sensing Short Test : RESULT: Fail
> Absolute Sensing Open Test : RESULT: Fail
I haven't seen other people with or without touch screen issues run this test, so it may or may not be an indicator that something's wrong with the touch screen or its kernel-side drivers. By the way, this doesn't require superuser. You can check this on any device and even use a good text editor like QuickEdit to open the file and generate test results.
At this point, I'm fairly content with the new improvements I've made, but my best bet on a complete fix would be upgraded touch drivers. The "Advanced In-Cell Touch" device this phone uses is pretty new. There's a good chance this technology has drivers that don't have all the bugs worked out. This is something we'll have to wait on. On the other hand, if LGE handed over a bootloader unlock method and some source files, I'd be just fine with that too.

What "issues" is this attempting to fix

kyle1867 said:
What "issues" is this attempting to fix
Click to expand...
Click to collapse
Probably the horrible touch response many users experience.

Is this something that we can copy and paste into the end of the build prop, or is it replacing stuff that is already there?
Sent from my LG-H811 using XDA Free mobile app

Wow nice job man.
Is it possible to address the swipe registering as taps through this or do you think this will also address it?

Harmtan2 said:
Is this something that we can copy and paste into the end of the build prop, or is it replacing stuff that is already there?
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
You'll have to add almost all of them.

Yes bro am too facing the touch problem in my intex aqua star power. The problem is when we keep the finger the screen shakes and also in 100% of my usage 20% touch mismatches . On first i irritated and now i habituated with this touch. [emoji28]
Sent from my Aqua Star Power using Tapatalk

The build.prop edits seem to be making the difference. ?
Sent From My LG G4

Rydah805 said:
The build.prop edits seem to be making the difference. ?
Sent From My LG G4
Click to expand...
Click to collapse
would you say that double tap to wake is improved as well?

esmenikmatixx said:
would you say that double tap to wake is improved as well?
Click to expand...
Click to collapse
Hmm, you know what, it is.
Sent From My LG G4

esmenikmatixx said:
would you say that double tap to wake is improved as well?
Click to expand...
Click to collapse
I would say so I have all these except the new ones he posted an an script from another post an I do see some improvements defiantly double tap to wake

GUGUITOMTG4 said:
You'll have to add almost all of them.
Click to expand...
Click to collapse
Soooo... can you run through this with me? I'm not a novice but I'm trying to figure out how to add them? I can't simply text edit the build.prop on my phone or pull/push from my computer?

This post is the reason why I'm glad we now have root.

Akomack said:
Soooo... can you run through this with me? I'm not a novice but I'm trying to figure out how to add them? I can't simply text edit the build.prop on my phone or pull/push from my computer?
Click to expand...
Click to collapse
Yes, you can manually edit it and or push pull it, but sometimes it causes bootloop when edited as a plain text. I would suggest using a build prop editor app from Play Store (I use Build Prop Editor by JRummy. It's Also built in in Rom Toolbox). You will have to copy-paste line by line. I'm gonna try those settings, but in my case, my screen sometimes misses when the phone gets hot. I attribute my touchscreen issues to the Lag LG injected on thermal files.

GUGUITOMTG4 said:
Yes, you can manually edit it and or push pull it, but sometimes it causes bootloop when edited as a plain text. I would suggest using a build prop editor app from Play Store (I use Build Prop Editor by JRummy. It's Also built in in Rom Toolbox). You will have to copy-paste line by line. I'm gonna try those settings, but in my case, my screen sometimes misses when the phone gets hot. I attribute my touchscreen issues to the Lag LG injected on thermal files.
Click to expand...
Click to collapse
Do you have to be rooted to do that?

Hendrycks said:
Do you have to be rooted to do that?
Click to expand...
Click to collapse
Yes you do
Sent from my LG-H811 using Tapatalk

Hi,
yesterday I bought a G4 H815.
I have the following problem: If my phone is on the bed next to me, or lying on a table, the touchscreen response is terrible. If I'm holding it in my hand, there's no problem. If it's charging and so lying on the bed, there's no problem either.
I took a few photos with my Optimus Black, since I could't take any screenshots of the issue:
this is with my phone lying on the bed:
and here holding it in my hands, producing no problems at all.
what is this? It's bloody annonying and totally unacceptable from a phone of this level, And yes... I would use it without holding it, just placing it on my bed next to me, but you can see how it is performing like so...
is my display faulty, or what?

Thanks man.
It's indeed more responsive. Especially double tap to wake is working good now.

*justintime* said:
Thanks man.
It's indeed more responsive. Especially double tap to wake is working good now.
Click to expand...
Click to collapse
I didnt feel a difference can you post a screenshot of your buildprop? Thanks in advance
Maybe im doing it wrong
Sent from my LG-H811 using Tapatalk

Just edit with es file Explorer.
And get the build.prop in the system folder. Not the other one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Increasing torch power with root

Does anyone know how to increase the torch power? Like z1-z2-z3 years ago?

DELETED - misread

Kianush said:
I havent heard of that and touch sensitivity is really good but I think you can increase it b enabling glove mode.
Click to expand...
Click to collapse
toRch not toUch :laugh:

gabed90 said:
Does anyone know how to increase the torch power? Like z1-z2-z3 years ago?
Click to expand...
Click to collapse
I haven't figured out how to increase the stock torch brightness the same way I could on the Z3c, but I found an okay workaround to override it temporarily. On the stock MM ROM I'm running, the brightness is controlled by two files: "/sys/class/leds/led:torch_0/brightness" and "/sys/class/leds/led:torch_1/brightness". You can edit these to any number (don't burn out your led....I haven't tried anything above 1000), then toggle on the torch by changing "/sys/class/leds/led:switch/brightness" to "1". The torch can then be turned off by changing "/sys/class/leds/led:switch/brightness" to "0". The stock flashlight brightness is "12", which is really dim, but "90" has been a good brightness for me so far.
I wrote a script (attached) which toggles the torch on and off with a "90" brightness. It has to be run with su (root).
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch/brightness)
if [ "$toggle" = "0" ];then
echo 90 > /sys/class/leds/led:torch_0/brightness
echo 90 > /sys/class/leds/led:torch_1/brightness
echo 1 > /sys/class/leds/led:switch/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_1/brightness
echo 0 > /sys/class/leds/led:switch/brightness
echo "off"
fi
Also I used Script Manager to set up a home screen widget to run this script, so I have a "bright torch" toggle on my home screen. Maybe someone could make this into an app so this solution wouldn't be quite as clunky.

Hi! Does it work? How can I install it?

I tried to do the widget, but when I start it , Permission denied appears.
I have rooted device, and I gave SM manager root permissions...

mains75 said:
I tried to do the widget, but when I start it , Permission denied appears.
I have rooted device, and I gave SM manager root permissions...
Click to expand...
Click to collapse
Do you have the "Su" toggle turned on for that script in SM Manager? It's in the top bar when you setup the script.

Yes I have..
After some attempts It worked... Thankyou
I wonder why if I edit the 2 files manually, system resets their value after you turn on the torch with other apps...

dog77k said:
I wrote a script (attached) which toggles the torch on and off with a "90" brightness. It has to be run with su (root).
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch/brightness)
if [ "$toggle" = "0" ];then
echo 90 > /sys/class/leds/led:torch_0/brightness
echo 90 > /sys/class/leds/led:torch_1/brightness
echo 1 > /sys/class/leds/led:switch/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_1/brightness
echo 0 > /sys/class/leds/led:switch/brightness
echo "off"
fi
Also I used Script Manager to set up a home screen widget to run this script, so I have a "bright torch" toggle on my home screen. Maybe someone could make this into an app so this solution wouldn't be quite as clunky.
Click to expand...
Click to collapse
Thank you - your script works well!
A minor issue is that when you run the script thru the widget shortcut, it pulls open the Script Manager app. Do you know any way to avoid this? Maybe an additional line in the script that kills the current app?
Thanks again.

Longhorn Android said:
Thank you - your script works well!
A minor issue is that when you run the script thru the widget shortcut, it pulls open the Script Manager app. Do you know any way to avoid this? Maybe an additional line in the script that kills the current app?
Thanks again.
Click to expand...
Click to collapse
Good idea. Add this line to end of the script and it will close Script Manager.
Code:
killall os.tools.scriptmanager

dog77k said:
Good idea. Add this line to end of the script and it will close Script Manager.
Code:
killall os.tools.scriptmanager
Click to expand...
Click to collapse
Thanks - that works perfectly.

xz1 compact
I tried to run this script on Sony XZ1 compact, but when running ScriptManager writes "No such file or directory". What am I doing wrong? ROOT mean. The path on the system and similar files exist. I turn on the SU button at startup. Help please.

dog77k said:
I haven't figured out how to increase the stock torch brightness the same way I could on the Z3c, but I found an okay workaround to override it temporarily. On the stock MM ROM I'm running, the brightness is controlled by two files: "/sys/class/leds/led:torch_0/brightness" and "/sys/class/leds/led:torch_1/brightness". You can edit these to any number (don't burn out your led....I haven't tried anything above 1000), then toggle on the torch by changing "/sys/class/leds/led:switch/brightness" to "1". The torch can then be turned off by changing "/sys/class/leds/led:switch/brightness" to "0". The stock flashlight brightness is "12", which is really dim, but "90" has been a good brightness for me so far.
I wrote a script (attached) which toggles the torch on and off with a "90" brightness. It has to be run with su (root).
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch/brightness)
if [ "$toggle" = "0" ];then
echo 90 > /sys/class/leds/led:torch_0/brightness
echo 90 > /sys/class/leds/led:torch_1/brightness
echo 1 > /sys/class/leds/led:switch/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_1/brightness
echo 0 > /sys/class/leds/led:switch/brightness
echo "off"
fi
Also I used Script Manager to set up a home screen widget to run this script, so I have a "bright torch" toggle on my home screen. Maybe someone could make this into an app so this solution wouldn't be quite as clunky.
Click to expand...
Click to collapse
Thanks for the guide, now I successfully edited my config, and I can use godly torch app to control light intensity.

Meh, get this little bugger.
Far brighter than any smartphone with easy charging. I wuv my copy
MicroStream® USB | Rechargeable LED Pocket Flashlight | Streamlight®

#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 90 > /sys/class/leds/led:torch_0/brightness
echo 90 > /sys/class/leds/led:torch_1/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_1/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Click to expand...
Click to collapse
i edit name folder switch to worck for xz3 i tested for me is worck good and plzz i need mehtod before edit in rom like defaut

Meh... bear in mind the led current was sinked at that level for a reason.
Although it goes much higher with the camera, it's only briefly.
Running it full time like that may exceed it's heat sinking capabilities and prematurely burn it out.
Everything happens for a reason... and it probably wasn't to keep you in the dark

plz i need methode for edit firmware or system for adjust torch

script worck for me for xperia xz3 by change switch to switch_0 and i need methode for set auto by sysytem