#!/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
Related
Can someone with a Droid 2 tell me what the Build.MODEL value is? Because of a bug in Droid X and Droid 2, I need to detect the devices and use a workaround. I know the Droid X MODEL string is "DroidX", so it's probably "Droid2", but confirmation would be nice!
The bug is that using TTS on the "alarm" audio stream causes beeping during phone calls. My app is "Good Morning" by Flywheel Consulting, for the curious. Thanks!
PHP:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=VZW
ro.build.display.id=VZW
ro.build.version.incremental=2.2.90
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Thu Aug 5 10:30:29 CDT 2010
ro.build.date.utc=1281022229
ro.build.type=user
ro.build.user=dbretzm1
ro.build.host=il93lnxdroid22
ro.build.tags=test-keys
ro.product.model=DROID2
ro.product.model.internal=A955
ro.product.brand=verizon
ro.product.name=droid2_vzw
ro.product.device=cdma_droid2
ro.product.board=droid2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=droid2_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_droid2-user 2.2 VZW 2.2.90 ota-rel-keys,release-keys
ro.build.fingerprint=verizon/droid2_vzw/cdma_droid2/droid2:2.2/VZW/22.90:user/ota-rel-keys,release-keys
# end build properties
#
# system.prop for CDMA Droid2
#
# rild.libpath=/system/lib/libril-moto-umts-1.so
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.default_usb_mode=2
# BEGIN Motorola, a18772, 05/19/2010, IKSHADOW-5584
# Add 411 to DAN List for VZW.
ro.mot.ril.danlist=611,*611,#611,411
# END IKSHADOW-5584
persist.ril.ecclist=911,*911,#911
persist.ril.modem.mode =1
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=55
# This defines the min duration between two pointer event
ro.min_pointer_dur=10
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=0
# Default network type.
# 4 => CDMA / EVDO.
ro.telephony.default_network=4
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
# wlan interface
wifi.interface = tiwlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=30m
# The URL for safety information
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=
# Enable HAC to also display Call Setting Menu Option.
ro.mot.hw.HAC=1
# Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android
# Property to set enabling state of the location privacy setting feature.
# Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067
#ro.mot.settings.locprivacy=1
# ERI feature
# 0 OFF
# 1 ON
ro.mot.eri=1
# Motorola, a22976, 13/5/2010, IKSHADOW-5203
# Delay for Loss Of Service alert
ro.mot.eri.losalert.delay=2000
# If time from last RoamInd change to SID change less than below, not play alert
ro.mot.eri.sidalert.delay=1000
# END IKSHADOW-5203
# Motorol,a6889c,02/Feb/2010,IKSHADOW-619
# Proximity Sensor feature
# 0 disable
# 1 enable
persist.mot.proximity.touch=1
# End IKSHADOW-619
# BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841
# VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING
# 0 disable
# 1 enable
ro.cdma.nbpcd=1
# END IKSHADOW-702
# BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone
# Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone
# persist.mot.powerup.tone=/system/media/bootup.ogg
# END IKSHADOW-1784
# BEGIN Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
ro.com.android.dataroaming=true
# END Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
persist.mot.a2dp.direct = 0
# System property for SMC
ro.service.start.smc=1
# BEGIN Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
# 0 disable
# 1 enable
persist.mot.usb.mediasync = 1
# END Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal BUA is preloaded, not allow to install standalone version of BuA from Android Market
# false Horizontal BUA is not preloaded
ro.HorizontalBUA=true
#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal VVM is preloaded, not allow to install standalone version of VVM from Android Market
# false Horizontal VVM is not preloaded
ro.HorizontalVVM=true
ro.mot.master_clear.shredsd=false
# BEGIN Motorola, pkd348, 09-July-2010, IKSTABLEONE-1236
# true enable the feature of In case of Emergency, default is false
# false disable the ICE feature
ro.mot.fid.29967.ice=true
# BEGIN MOTOROLA, vfhk68,24-July-2010, IKSTABLEONE-2469
# true enable the feature of 33531
# false disable the feature
ro.mot.fid.33531.keylock_ecm=true
#END
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.kernel.android.ril=yes
persist.ril.mux.noofchannels=7
persist.ril.mux.ttydevice=/dev/ttyS0
persist.ril.modem.ttydevice=/dev/ttyUSB0
persist.ril.features=0x07
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
ro.config.notification_sound=Droid.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.telephony.sms_segment_size=160
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r3
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=A855
ro.setupwizard.enable_bypass=1
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.media.capture.maxres=5m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.classification=classE
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.config.version=GAS_NA_DROID2VZW_P011
ro.build.config.date=Thu_Aug_05_10:28:58_-0500_2010
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
ro.build.version.full=Blur_Version.2.2.90.A955.Verizon.en.US
ro.config.ringtone=DroidTestLab.ogg
@theecho,
Wow!! LOL
Sent from my DROID2 using XDA App
Was just a simple copy and paste from the system dump released months ago.
It seems like this is a constant issue among most of us. Here are some workarounds and/or fixes. We could use this thread to discuss auto-brightness and whatnot:
Guhrasoh said:
If it isn't working edit /system/etc/hw_config.sh and change this line:
Code:
echo i2c > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/mode # i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als
into this:
Code:
echo i2c[B]_als[/B] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/mode # i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als
It's working here, do you have the latest version of it?
Click to expand...
Click to collapse
porio said:
AFAIU, the brightness controlling chip or driver in our X8 has three modes. als, if enabled, reads the light sensor and sets the brightness according to it. In other words, is a hardware based auto brightness. i2c and pwm are the other two modes, for direct brightness control but I don't understand the difference between them. If two or three modes are enabled, the output (brightness) is a mixture of all.
So, if you set something like als_pwm or i2c_als or i2c_als_pwm, you will have auto-brightness even if you don't set it in your device; it will work like in a hardware layer (so to speak). The best setting for me is to enable i2c_als_pwm and set the brightness to something like 40 or 50%. For some reason it didn't work well in GDX 006 but in 007 is working OK. It also help if you set the line
Code:
echo 512 > /sys/devices... ...0036/als::avg-t # 32,....
The lower the value, more flicker you will have. 512 seems to be reasonable.
BTW I this I learned this here: http://www.national.com/pf/LM/LM3530.html#Overview
The pdf datasheet has lots of info.
Regards
Click to expand...
Click to collapse
Some useful settings if you don't want to edit the lines:
mr-tical said:
Code:
0 25
2000 35
4000 40
5500 50
7000 60
8500 70
10100 80
20100 90
30100 100
40100 120
50100 150
60100 180
70100 210
80100 240
90100 255
102000 255
{
"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"
}
With these levels i think display lighting and dimming is smoother, but i got one more guestion - how can i force to read faster the light value form sensor for guicker adjusting the display changing display levels, i mean, if he can do it faster?
Click to expand...
Click to collapse
Ok, so this is hw_config.sh sensor configuration for X8 (one of the most decent ones), I believe it was enhanced by the user alfasamsung.
Code:
# lm3530 LMU configuration
echo linear > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::mapping # linear exp
echo 32768 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::rate::up # 8, 1024, 2048, 4096, 8192, 16384, 32768, 65538
echo 32768 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::rate::down # 8, 1024, 2048, 4096, 8192, 16384, 32768, 65538
echo 250 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::limit # 0 - 255
echo 12.0 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::fsc # 5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5
echo 4,16,64,250 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/curve::borders
echo 47,75,114,164,226 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/curve::targets
echo high-z > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/als::r1 # high-z, 9360, 5560 .. 677.6 (see chip mnual)
echo high-z > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/als::r2 # high-z, 9360, 5560 .. 677.6 (see chip mnual)
echo [COLOR="Red"]1024[/COLOR] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/als::avg-t # 32, 63, 128, 256, 512, 1024, 2048, 4096
echo i2c_pwm > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/mode # i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als
what are the suggestions, besides changing the number in red to 512???
what if we try changing the last line to:
Code:
echo [B][COLOR="Green"]i2c_pwm_als[/COLOR][/B] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/mode # i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als
When i used i2c_pwm_als my phone become unstable. Its hard to wake it up and causes reboot. I dont know with others.
What about CyanogenMOD settings ->Display - > Automatic Backlight?
There a lot settings to play with there..
Dare-Devil Inside said:
What about CyanogenMOD settings ->Display - > Automatic Backlight?
There a lot settings to play with there..
Click to expand...
Click to collapse
It will not work
Sent from X8 using XDA Premium app and running GingerDX
This is my understanding of the values and how it works.
We have two modes to choose from in hw_config.sh :/sys/devices/platform/i2c-adapter/i2c-0/0-0036/mode
i2c or i2c_als.i2c just enables the sensor and i2c_als means that the sensor controlls the brightness in automatic mode(hardware layer)
In cm roms I recomend using i2c mode and let the framework controll the brightness.Only problem here is that we have to set the values in the framework.The standard setting is not for the x8 sensor,they are way of.We need to go to cm setting>display>Aut. backlight>tick use custom and allow light decrease>edit levels and put in somethin like this(see pictures)
Back too the values in hw_config:
i2c mode:
-br::rate::up and down -how long it takes to change the light from one step to anoter.this is a value in ms.high value the light will change slow.low value it goes fast
- br::fsc -this is the max current the screen can use. higer value will give brighter screen at max value.
i2c_als mode:
-br::limit -this is max brightness
-curve::borders -these are the borders in your light curve
-curve::targets -targets for the light curve.Here you sett the lovest and higest brightness values (in a curve)
-als::avg-t -how often the sensor updates the screen in mseconds.It sets the screen to the average value in this time period.Has no inpact on i2c mode.
This is my current config:
Code:
echo linear > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::mapping # linear exp
echo [B]8192[/B] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::rate::up # 8, 1024, 2048, 4096, 8192, 16384, 32768, 65538
echo [B]65538[/B] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::rate::down # 8, 1024, 2048, 4096, 8192, 16384, 32768, 65538
echo 250 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::limit # 0 - 255
echo [B]19.0[/B] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/br::fsc # 5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5
echo 30,70,110,150 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/curve::borders
echo 10,75,120,164,254 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/curve::targets
echo high-z > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/als::r1 # high-z, 9360, 5560 .. 677.6 (see chip mnual)
echo high-z > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/als::r2 # high-z, 9360, 5560 .. 677.6 (see chip mnual)
echo 1024 > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/als::avg-t # 32, 63, 128, 256, 512, 1024, 2048, 4096
echo [B]i2c[/B] > /sys/devices/platform/i2c-adapter/i2c-0/0-0036/mode # i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als
with the correct settings in cm settings this works great.
You can check that your sensor works by going to cm settings.........edit other levels and there you see the value of the sensor in the top.
Puh this was a long post
Forgot the pwm mode:this is for external input.
Rom builders please change the array in the framework-res.> res\values\arrays.
Update: Added a very nice picture trying to explain borders and targets in i2c_als mode
@alfsamsung , i applied this change in attached hw_config.sh and replace it
i think it shold be true but again AutoBrightness works wrongly
please if you can take a look on it ,thanks
EDIT : guys u can use the attached hw_config.sh for GingerDX v007
alfsamsung confirmed it and it works well
EDIT 2 : here for GDX 007
X1111 said:
@alfsamsung , i applied this change in attached hw_config.sh and replace it
i think it shold be true but again AutoBrightness works wrongly
please if you can take a look on it ,thanks
Click to expand...
Click to collapse
The hw_config.sh looks good. Did you edit the settings in cmSettings>Automatic backlight? Do you see any values in the Edit other leves.. when you put the phone under some light?
alfsamsung said:
The hw_config.sh looks good. Did you edit the settings in cmSettings>Automatic backlight? Do you see any values in the Edit other leves.. when you put the phone under some light?
Click to expand...
Click to collapse
no ,do i this setting like this picture you mean ? or what setting must i change please ?
thanks for response
X1111 said:
no ,do i this setting like this picture you mean ?
thanks for response
Click to expand...
Click to collapse
Yes.Just change the values on the left side to something similiar with the picture.Play with the values to you get it to your liking.
alfsamsung said:
Yes.Just change the values on the left side to something similiar with the picture.Play with the values to you get it to your liking.
Click to expand...
Click to collapse
oh ,seems work ,thanks man
and how many levels need to have for best setting ?
EDIT : what amounts must be in screen column ? i cant change them similar to the picture
X1111 said:
oh ,seems work ,thanks man
and how many levels need to have for best setting ?
Click to expand...
Click to collapse
Don't know.Again you need to play with these settings and find what you like.I have 14.To many the backlight will change to often.There is a problem with the levels on the right side.You can't enter a value under 20.I had to rebuild the framework to get my settings.
@alfsamsung, how do you change the value of screen on CM automatic backlight settings ???
Ps: on that screen of configurations of custom levels, My screen on the top of page shows disabled.
biscoitu said:
@alfsamsung, how do you change the value of screen on CM automatic backlight settings ???
Ps: on that screen of configurations of custom levels, My screen on the top of page shows disabled.
Click to expand...
Click to collapse
for change the value of screen you must change from bottom
change the lowest to 255
X1111 said:
for change the value of screen you must change from bottom
change the lowest to 255
Click to expand...
Click to collapse
hmmm, I will try it , let´s have fun with this features
biscoitu said:
hmmm, I will try it , let´s have fun with this features
Click to expand...
Click to collapse
i adjust it according the pic and light sensor is working much better than befor
all thanks refers to alfsamsung
biscoitu said:
@alfsamsung, how do you change the value of screen on CM automatic backlight settings ???
Ps: on that screen of configurations of custom levels, My screen on the top of page shows disabled.
Click to expand...
Click to collapse
If the value is disabled you need to turn on automatic brightness in the android screen settings. Or if you are on i2c_als mode you need to change hw_config to i2c
I got it working, but I´m confused . It lights up when in light, but it doesn´t return to the original bright when I cover the sensor . There it shows that is filtering, but my screen stills brighter :/
Edit: I´m already enabled and trying set many values there. Only one information at the cm settings menu, what do you put on Reset Threshold, Window Lenght and Sample Interval??
biscoitu said:
I got it working, but I´m confuse . It lights up when in light, but it doesn´t return to the original bright when I cover the sensor . There it shows that is filtering, but my screen stills brighter :/
Click to expand...
Click to collapse
You need to enable allow light decrease.One screen back from the values
alfsamsung ,
i tested it at sunshine and brightness went into 255 ,and then at darkness it went into lowest value
but it seems increasing acts better than decreasing...
Hi there
Just got GS5, ultra power saving mode is sweet however is there a way to automatically turn it on at a certain % of remaining battery (e.g. at 10% it turns on)
ALL help and advice welcome
It only takes one finger swipe and touch to activate it. Don't be too lazy now.
Sent from my SM-G900F using Tapatalk
Simone said:
It only takes one finger swipe and touch to activate it. Don't be too lazy now.
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
The reason I ask is that if I leave my phone out overnight after a night out etc I don't want to wake up in the morning to a dead battery. Instead having it auto switch will be life saving ..ha :good:
I'm not 100% sure but I'm assuming you could probably create a Tasker profile to trigger UPSM at a specific battery percentage.
I have very little experience with Tasker though so someone correct me if I'm wrong.
Sent from my SM-G900W8 using Tapatalk
1742
msavic6 said:
I'm not 100% sure but I'm assuming you could probably create a Tasker profile to trigger UPSM at a specific battery percentage.
I have very little experience with Tasker though so someone correct me if I'm wrong.
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
Hi there
Thanks v much for the info/ idea. I'll look into it, do I need to root my gs5 for tasker??
anyone else have knowledge activating upsm at a certain battery %.
Thanks
Unfortunately, Tasker has no possibilty to enable UPSM
The Tasker has possibility to lunch external script or application, but the problem is that there is no script which can start UPSM.
Is somebody found a way to do it? May-be another ways?
Somebody on reddit has been working with Tasker to do this. I can't post the link since I haven't posted more than 10 times, so do a google search for "Figured out how to activate Ultra power saver mode" reddit and tasker. It should come up.
I've tried it and had some success with it, but having some issues with the second tap command to activate. Seems like I had to up the timeout to something like 15 seconds.
Good luck.
Yes! You can
Using tasker of course
1. You have to put U.power saving somewhere on the visible part of Notification panel - pic 1
2. Create profile - State - Power - Battery level - (from 0 to 10 for example) - pic 2
3. Create new task: - pic 3
1. Display - Status Bar - Expanded
2. Script - Run Shell - Command - input tap x y (where x y are coordinates of the buttons you want to tap), check Use Root option
3. Script - Run Shell - Command - input tap x y (button OK on the UPSM menu), check Use Root option - pic 4
In my case x=972 y=226 and
x=790 y=1600
You have to check your x and y coordinates by turning Show pointer location in Developer options
And now you will have Ultra Power Saving Mode when your battery reaches 10 %
I would like this feature as well.. makes sense to me. I mean if the camera can stop the flash from working on low battery then enabling UPSM at low battery should be an option
nice but ...
This is really nice solution to automatically enable UPSM but one remark ... screen has to be turned on and screen locker must be unlocked ... so is we are already watching on phone why shouldn't we just manually start UPSM ?
Do you have any idea how to enable UPSM fully automatically ? without even touching phone ? my idea is to forget about power problems and every time when my phone will reach 5% it will automatically turn on UPSM completely without me.
ciechom said:
This is really nice solution to automatically enable UPSM but one remark ... screen has to be turned on and screen locker must be unlocked ... so is we are already watching on phone why shouldn't we just manually start UPSM ?
Do you have any idea how to enable UPSM fully automatically ? without even touching phone ? my idea is to forget about power problems and every time when my phone will reach 5% it will automatically turn on UPSM completely without me.
Click to expand...
Click to collapse
ROOT REQUIRED
Try this :
this will unlock and run UltraPowerMode at the specified time (00:50)
On shell code :
Code:
mount -o rw,remount /system ; mv /data/system/gesture.key /data/system/oldgesture.key ; input keyevent 26 ; input swipe 71 500 636 500 ; mv /data/system/oldgesture.key /data/system/gesture.key ; mount -o ro,remount /system ; am start -n com.android.settings/.Settings\$UltraPowerSavingModeActivity ; input tap 670 103 ; input tap 520 1150
#change ro(readonly) to rw(read/write) and add the remount option
mount -o rw,remount /system
#Unlock device-- 1-PATTERN
mv /data/system/gesture.key /data/system/oldgesture.key
OR
#Unlock device-- 2-PIN LOCK
mv /data/system/password.key /data/system/oldpassword.key
#wakeup device
input keyevent 26 ; input swipe 71 500 636 500
#turn on original lock pattern
mv /data/system/oldgesture.key /data/system/gesture.key
OR
#turn on original lock PIN CODE
mv /data/system/oldpassword.key /data/system/password.key
#remount with the original readonly.
mount -o ro,remount /system
#start ultra power save menu
am start -n com.android.settings/.Settings\$UltraPowerSavingModeActivity
#command to touch the buttons
input tap 670 103 ; input tap 520 1150
flaviofire said:
Try this :
. . .
Click to expand...
Click to collapse
I will try it for sure thx mate
But one more question. I own Galaxy Alpha and I'm using finger to unlock my phone.
Which file shoud I move to Unlock device ? is it /data/system/fingerprintpassword.key ?
And can you please explain a little bit more what this will do:
"input keyevent 26 ; input swipe 71 500 636 500"
does those numbers 71 500 636 500 are important ? I'm wondering because it might differ in different phones
Thank you :thumbup: I'm looking for this.
This is good but can we do it so it starts at a specific battery level instead of time?
Thanks.
No idea how to do it that is why I asked.
flaviofire said:
ROOT REQUIRED
Try this :
this will unlock and run UltraPowerMode at the specified time (00:50)
On shell code :
Code:
mount -o rw,remount /system ; mv /data/system/gesture.key /data/system/oldgesture.key ; input keyevent 26 ; input swipe 71 500 636 500 ; mv /data/system/oldgesture.key /data/system/gesture.key ; mount -o ro,remount /system ; am start -n com.android.settings/.Settings\$UltraPowerSavingModeActivity ; input tap 670 103 ; input tap 520 1150
#change ro(readonly) to rw(read/write) and add the remount option
mount -o rw,remount /system
#Unlock device-- 1-PATTERN
mv /data/system/gesture.key /data/system/oldgesture.key
OR
#Unlock device-- 2-PIN LOCK
mv /data/system/password.key /data/system/oldpassword.key
#wakeup device
input keyevent 26 ; input swipe 71 500 636 500
#turn on original lock pattern
mv /data/system/oldgesture.key /data/system/gesture.key
OR
#turn on original lock PIN CODE
mv /data/system/oldpassword.key /data/system/password.key
#remount with the original readonly.
mount -o ro,remount /system
#start ultra power save menu
am start -n com.android.settings/.Settings\$UltraPowerSavingModeActivity
#command to touch the buttons
input tap 670 103 ; input tap 520 1150
Click to expand...
Click to collapse
Thanks for posting. Status bar -> set expanded does not work on my lollipop latest firmware phone. I figured out the XY in developer mode and tested my script, steps 2 and 3 are working, but step 1 seems to no longer work for lollipop. Do you have another method for getting the new taskbar to come down?
ivankolev said:
Yes! You can
Using tasker of course
1. You have to put U.power saving somewhere on the visible part of Notification panel - pic 1
2. Create profile - State - Power - Battery level - (from 0 to 10 for example) - pic 2
3. Create new task: - pic 3
1. Display - Status Bar - Expanded
2. Script - Run Shell - Command - input tap x y (where x y are coordinates of the buttons you want to tap), check Use Root option
3. Script - Run Shell - Command - input tap x y (button OK on the UPSM menu), check Use Root option - pic 4
In my case x=972 y=226 and
x=790 y=1600
You have to check your x and y coordinates by turning Show pointer location in Developer options
And now you will have Ultra Power Saving Mode when your battery reaches 10 %
Click to expand...
Click to collapse
:good:
Thanks for the post. Hopefully Tasker is working on adding UPSM in a future update.
rickneworleansla said:
:good:
Thanks for the post. Hopefully Tasker is working on adding UPSM in a future update.
Click to expand...
Click to collapse
If you´re rooted. Install secure settings plugin it works with Tasker
I solved the problem
Open quick settings and then use AutoInput to click ultra saving mode and ok (or whatever the prompt). Make sure to include wait tasks to pause for sufficient time so everything have chance to happen.
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
Hi, i cannot connect to public wifi with a
spoofed mac adress but it work good with the
permanent hardware mac adress ; and my laptop can
connect with a spoofed mac adress so the problem
come from my phone, a motorola moto g4 play.
I use ifconfig or macchanger
i find this kind of file on the phone, maybe
they have no importance :
/system/etc/firmware/wlan/prima/WCNSS_cfg.dat :
I can't read
/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini :
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
gEnableMacAddrSpoof=1
#Enable/Disable Link Layer Statistics Feature
gEnableLLStats=1
#Enable/Disable EXTScan Feature
gEnableEXTScan=1
gBtcFastWlanConnPref=0
gBtcEnableIndTimerVal=5
gEnableTDLSScan=1
gTDLSExternalControl=1
gEnableTDLSSupport=1
gEnableTDLSImplicitTrigger=1
gTDLSTxStatsPeriod=500
gTDLSTxPacketThreshold=10
gTDLSDiscoveryPeriod=20000
gTDLSMaxDiscoveryAttempt=5
gTDLSIdleTimeout=40000
gTDLSRssiHysteresis=100
gTDLSIdlePacketThreshold=5
gEnableTDLSScanCoexistence=1
#Splitscan related params
gPassiveMaxChannelTimeConc=110
gPassiveMinChannelTimeConc=60
gRestTimeConc=100
gActiveMinChannelTimeConc=20
gActiveMaxChannelTimeConc=27
gNumStaChanCombinedConc=1
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
# 0 implies no periodic wake up from IMPS. Periodic wakeup is
# unnecessary if Idle Scan is disabled.
gImpsModSleepTime=0
# Diable administered P2P device
isP2pDeviceAddrAdministrated=0
# Enable BMPS or not
gEnableBmps=1
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
# Valid values are 0-9, with 0 = Auto, 4 = 11n, 9 = 11ac
gDot11Mode=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# Assigned MAC Addresses - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
Intf0MacAddress=000AF58989FF
Intf1MacAddress=000AF58989FE
Intf2MacAddress=000AF58989FD
Intf3MacAddress=000AF58989FC
# Set/Clear UAPSD mask
UapsdMask=0
# UAPSD service interval for VO,VI, BE, BK traffic
UapsdMask=0
InfraUapsdVoSrvIntv=20
InfraUapsdViSrvIntv=40
# Flag to allow STA send AddTspec even when ACM is Off
gAddTSWhenACMIsOff=1
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
# WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=0
#Enable NDP offload
hostNSOffload=1
#Flag to enable HostARPOffload feature or not
hostArpOffload=1
#SoftAP Related Parameters
# AP MAc addr
gAPMacAddr=000AF589dcab
# 802.11n Protection flag
gEnableApProt=1
#Enable OBSS protection
gEnableApOBSSProt=1
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=1
# Fixed Rate
gFixedRate=0
# Maximum Tx power
# gTxPowerCap=30
# Fragmentation Threshold
# gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM Enable/Disable
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=0
# CCX Support and fast transition
EseEnabled=0
FastTransitionEnabled=1
ImplicitQosIsEnabled=0
gNeighborScanTimerPeriod=200
# default value of this parameter is zero to enable dynamic threshold allocation
# to set static roming threshold uncomment below parameter and set vaule
#gNeighborLookupThreshold=78
gNeighborScanChannelMinTime=20
gNeighborScanChannelMaxTime=30
# Legacy (non-CCX, non-802.11r) Fast Roaming Support
# To enable, set FastRoamEnabled=1
# To disable, set FastRoamEnabled=0
FastRoamEnabled=1
#Check if the AP to which we are roaming is better than current AP in terms of RSSI.
#Checking is disabled if set to Zero.Otherwise it will use this value as to how better
#the RSSI of the new/roamable AP should be for roaming
RoamRssiDiff=5
# SAP Country code
# Default Country Code is 2 bytes, 3rd byte is optional indoor or out door.
# Example
# US Indoor, USI
# Korea Outdoor, KRO
# Japan without optional byte, JP
# France without optional byte, FR
#gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
gShortGI40Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
# SAP auto channel selection configuration
# 0 = disable auto channel selection
# 1 = enable auto channel selection, channel provided by supplicant will be ignored
gApAutoChannelSelection=0
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 97 dBm.
#
gEnablePhyAgcListenMode=128
#Preferred channel to start BT AMP AP mode (0 means, any channel)
BtAmpPreferredChannel=0
#Preferred band (both or 2.4 only or 5 only)
BandCapability=1
#Beacon Early Termination (1 = enable the BET feature, 0 = disable)
enableBeaconEarlyTermination=1
beaconEarlyTerminationWakeInterval=11
#Bluetooth Alternate Mac Phy (1 = enable the BT AMP feature, 0 = disable)
gEnableBtAmp=0
#SOFTAP Channel Range selection
gAPChannelSelectStartChannel=1
gAPChannelSelectEndChannel=11
#SOFTAP Channel Range selection Operating band
# 0:2.4GHZ 1: LOW-5GHZ 2:MID-5GHZ 3:HIGH-5GHZ 4: 4.9HZ BAND 5: 5GHZ BAND
gAPChannelSelectOperatingBand=0
#Channel Bonding
gChannelBondingMode5GHz=1
gEnableModulatedDTIM = 3
gMaxLIModulatedDTIM = 3
gEnableDatainactivity = 200
#Enable Keep alive with non-zero period value
gStaKeepAlivePeriod=30
#Say gGoKeepAlivePeriod(5 seconds) and gGoLinkMonitorPeriod(10 seconds).
#For every 10 seconds DUT sends Qos Null frame(i.e., Keep Alive frame if link is idle for last 10 seconds.)
#For both active and power save clients.
#Power save clients: DUT set TIM bit from 10th second onwards and till client honors TIM bit.
#If doesn't honor for 5 seconds then Driver remove client.
#Active clients: DUT send Qos Null frame for 10th seconds onwards if it is not success still DUT try on
#11th second if not tries on 12th and so on till 15th second. Hence before disconnection DUT will send 5 NULL frames.
#Hence in any case DUT will detect client got removed in (10+5) seconds. i.e., (gGoKeepAlivePeriod +gGoLinkMonitorPeriod)..
#gGoLinkMonitorPeriod/ gApLinkMonitorPeriod is period where link is idle and it is period
#where we send NULL frame.
#gApLinkMonitorPeriod = 10
#gGoLinkMonitorPeriod = 10
#gGoKeepAlivePeriod/gApKeepAlivePeriod is time to spend to check whether frame are succeed to send or not.
#Hence total effective detection time is gGoLinkMonitorPeriod+ gGoKeepAlivePeriod/gApLinkMonitorPeriod+ gApKeepAlivePeriod.
gGoKeepAlivePeriod = 10
gApKeepAlivePeriod = 60
#If set will start with active scan after driver load, otherwise will start with
#passive scan to find out the domain
#gEnableBypass11d=1
#If set to 0, will not scan DFS channels
gEnableDFSChnlScan=1
gEnableLogp=1
# Enable Automatic Tx Power control
gEnableAutomaticTxPowerControl=0
# 0 for OLPC 1 for CLPC and SCPC
gEnableCloseLoop=1
#Data Inactivity Timeout when in powersave (in ms)
gDataInactivityTimeout=110
gEnableLpwrImgTransition=1
#If set to 0, MCC is not allowed.
gEnableMCCMode=0
# Priority Setting:COUNTRY IOCTL > 11d > NV default
gCountryCodePriority=1
#Count of the Scan Result age.
gScanResultAgeCount=2
#Enable Scan Results Aging based on timer
#Timer value is in seconds
#If Set to 0 it will not enable the feature
gScanAgingTime=10
# Scan Timing Parameters
# gPassiveMaxChannelTime=110
# gPassiveMinChannelTime=60
# Enable Tx LDPC
#gTxLdpcEnable = 1 for HT mode, 2 for VHT mode,3 for both HT and VHT
gTxLdpcEnable=3
# gActiveMaxChannelTime=40
# gActiveMinChannelTime=20
# Valid values are 2048,4096,8192 and so on
# Please don't use values other than the ones mentioned above
gMaxMediumTime=4096
# 802.11K support
gRrmEnable=1
gRrmOperChanMax=8
gRrmNonOperChanMax=8
gRrmRandIntvl=100
#Scan offload
gEnableDirectedScanOffload=0
#FlexConnect Power Factor
#Default is set to 0 (disable)
gFlexConnectPowerFactor=0
#SAP/P2P-GO mode traffic monitor
gEnableTrafficMonitor=0
gTrafficIdleTimeout=3000
#gAdvertiseConcurrentOperation=0
gVhtChannelWidth=2
# VHT Tx/Rx MCS values
# Valid values are 0,1,2. If commented out, the default value is 0.
# 0=MCS0-7, 1=MCS0-8, 2=MCS0-9
gVhtRxMCS=2
gVhtTxMCS=2
# Enable Tx beamforming
gTxBFEnable=1
#Enable/Disable TDLS Feature
gEnableTDLSSupport=1
#Enable/Disable TDLS Implicit Trigger
gEnableTDLSImplicitTrigger=0
#Enable/Disable TDLS WMM Mode
gEnableTDLSWmmMode=1
#Enable/Disable TDLS Buffer Sta
gEnableTDLSBufferSta=1
#Enable mac spoofing for firmware scans only (disabled in host scans)
gEnableMacAddrSpoof=2
#Disable Fatal event
gEnableFatalEvent=0
#gEnableRtsCtsHtVht=1
gEnableDynamicRAstartRate=1
#Enable Toggle ARP BD Rates
gToggleArpBDRates=1
#Disable multicast host fw logs
gMulticastHostMsgs=0
# Configure 60ms for BT, 60ms for WLAN
# Default values are WLAN 30ms, BT 120ms
btcStaticLenLeWlan=60000
btcStaticLenLeBt=60000
gIgnorePeerErpInfo=0
SARPowerBackoff=0
END
# Note: Configuration parser would not read anything past the END marker
/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin :
I can't read
/sys/devices/soc.0/a000000.qcom,wcnss-wlan/wcnss_mac_adrr :
Code:
00:00:00:00:00:00
/sys/fs/selinux/class/capability2/perms/mac_admin :
Code:
2
/sys/fs/selinux/class/capability2/perms/mac_override
Code:
1
I think i am not the only one who have this problem, Thank for all answer.