So after a week on cm7 i've decided to go back to my zckpa chinese rom. cm7 is not that stable for now, and most of its features i can get with zckpa rom. but the thing that still bugging stock/custom rom based on stock is sod. from my experience its caused by wifi, when the phone get out of known wifi range and it constantly scanning, it get sod. then i found this little app that solve my sod problem. u need to be rooted to try this btw.
1- edit build.prop file, add this line in it
Code:
wifi.supplicant_scan_interval=300
and save it. 300 means 5 minutes, but u can use other value eg 600 which is 10 minutes. by doing this we limit phone scanning wifi interval.
2- install wififixer from market. set it:
"set wifi usability" i use "max battery"
tick on "enable wifi lock"
"wifi sleep policy" to "never"
and i've never got sod for almost a week
btw i dont use android default wifi scanning, i just let wififixer do its job in the background. not just its solve my sods problem, it also gave me stable connection, no constant signal dropping for me now
an0nym0us_ said:
So after a week on cm7 i've decided to go back to my zckpa chinese rom. cm7 is not that stable for now, and most of its features i can get with zckpa rom. but the thing that still bugging stock/custom rom based on stock is sod. from my experience its caused by wifi, when the phone get out of known wifi range and it constantly scanning, it get sod. then i found this little app that solve my sod problem. u need to be rooted to try this btw.
1- edit build.prop file, add this line in it
Code:
wifi.supplicant_scan_interval=300
and save it. 300 means 5 minutes, but u can use other value eg 600 which is 10 minutes. by doing this we limit phone scanning wifi interval.
2- install wififixer from market. set it:
"set wifi usability" i use "max battery"
tick on "enable wifi lock"
"wifi sleep policy" to "never"
and i've never got sod for almost a week
btw i dont use android default wifi scanning, i just let wififixer do its job in the background. not just its solve my sods problem, it also gave me stable connection, no constant signal dropping for me now
Click to expand...
Click to collapse
im still trying to figure out why wifi scanning will cause sod.
well theres another file, /system/etc/firmware/wlan/qcom_cfg.ini which control wifi driver in stock rom. cm doesnt have this. its content is:
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
gImpsModSleepTime=600
# 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)
gDot11Mode=0
# Handoff Enable(1) Disable(0)
gEnableHandoff=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# STA MAC Address - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
NetworkAddress=000AF58989FF
# UAPSD service interval for VO,VI, BE, BK traffic
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
InfraUapsdBeSrvIntv=0
InfraUapsdBkSrvIntv=0
# Disable RSSI FW filtering
gEnableFWRssiMonitoring=0
# 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
gEnableLogp=1
#SoftAP Related Parameters
# AP MAC address
gAPMacAddr=00deadbeef11
# 802.11n Protection flag
gEnableApProt=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 mode: Auto(0) or QBSS(1) or No-QoS(2)
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=1
# Country code
gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
#Enable OBSS protection
gEnableApOBSSProt=0
# Frames Processing Minimum Threshold
gMinFramesProcThres=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
END
# Note: Configuration parser would not read anything past the END marker
but i dont have any slight idea what those value means
I hate haptic feedback / vibration and have always disabled it completely in other Android tablets I have.
I already tried the known methods to disable haptic / vibration:
(1) Settings -> Sound -> uncheck vibrate
(2) terminal emulator: su, then chmod 0444 /sys/class/timed_output/vibrator/enable
I am surprised that (2) cannot completely disable haptic / vibration - OK the usual keyboards give no haptic feedback (because I specifically disabled it in the KB options), but other apps such as Calculator (keypad) and Fruit Slice (when you hit a bomb) still gives me haptic feedback, and the device still vibrates when it shuts down.
NOTE: I have already tried Vibrafix which does not work. I have also tried putting the "chmod 0444" command line into Script Manager and run it "su" (this is basically what Vibrafix does anyway), but it also did not work.
The closest cousin of the Galaxy Player is the Galaxy Tab (original 7 incher) - I had no problem disabling vibration on my GT using Vibrafix / chmod 0444, so why can I not do the same in the Galaxy Player?
VibraFix works great for me.
Just have to kill it after your re-enable vibes.
(it gets cranky)
slim_thumb said:
I hate haptic feedback / vibration and have always disabled it completely in other Android tablets I have.
I already tried the known methods to disable haptic / vibration:
(1) Settings -> Sound -> uncheck vibrate
(2) terminal emulator: su, then chmod 0444 /sys/class/timed_output/vibrator/enable
I am surprised that (2) cannot completely disable haptic / vibration - OK the usual keyboards give no haptic feedback (because I specifically disabled it in the KB options), but other apps such as Calculator (keypad) and Fruit Slice (when you hit a bomb) still gives me haptic feedback, and the device still vibrates when it shuts down.
NOTE: I have already tried Vibrafix which does not work. I have also tried putting the "chmod 0444" command line into Script Manager and run it "su" (this is basically what Vibrafix does anyway), but it also did not work.
The closest cousin of the Galaxy Player is the Galaxy Tab (original 7 incher) - I had no problem disabling vibration on my GT using Vibrafix / chmod 0444, so why can I not do the same in the Galaxy Player?
Click to expand...
Click to collapse
If all else fails, you can recompile the kernel with CONFIG_VIBETONZ=n, but I agree, there should be an easier way. Try (as root) 'rmmod vibrator', as it looks like the driver is compiled as a module.
Well you can always take the motor out, works 100%
Sent from my YP-G70 using xda app-developers app
Hi all,
does anybody know what to change in system to increase light of keys?? thanks for answer
It's connected to screen brightness. If you set your screen brightness higher, the LED bar will be brighter as well... And the other way around.
good point but I need to increase just keylight, it has to be changeable in some text file in system but I have no idea where..
OK, so I found it
It is in sys/class/leds/so34-led1 & so34-led2 & so34-led0 /brightness & max_brightness
but when I change number in brightness from stock 45 to 150 and save, then it's lighting more, but after close Root explorer, it's the same like before and it will return to 45.. what should I do? make init.d skript??
i also tried it, But same thing happens Value gets Changed to default,,,
can any script b made,,,
I think we should find some configuration file for auto brightness, coz the value in bightness file is changing by current light
ok, so I made init.d script, it actually works, but just until normal automatic change of brightness (for example, when turn screen off, or with light sensor changes..) you can't see any changes on startup too, so you have to force start the script (via root explorer click on script and choose "open with Linux Script handler" and then choose "execute", then the lights will be brighter, you can try it for test
Code:
#!/system/bin/sh
echo 255 > /sys/class/leds/so34-led0/brightness
echo 255 > /sys/class/leds/so34-led1/brightness
echo 255 > /sys/class/leds/so34-led2/brightness
but I think I should make different script.. unfortunatelly I don't know where is some configuration file for control of leds or light sensor or something.. I am just a nooby yet..
The backlight of the Alcatel One Touch Evolve won’t get any dimmer if you set the brightness below 40 or so (out of 255). I tried RootDim, and it didn’t work any better. Neither did
Code:
echo 10 > /sys/class/leds/lcd-backlight/brightness
Any values before 40 look as bright as 40 does. But this works, if you are rooted:
Code:
echo 20 > /sys/class/leds/lcd-backlight/brightness
echo 3 > /sys/class/leds/lcd-backlight/duty
"duty" apparently designates the pulse width modulation duty cycle. Setting the duty cycle to anything between 3 and 20 will make the screen dimmer than the minimum setting you can get with the normal brightness controls. Setting to 2 turns the screen entirely black, on my phone. The maximum value is 63.
Another way to set this is in the engineer mode that you can access by dialing *#*#3646633#*#*. Swipe to “Hardware Testing” and select “Display.” You can set a PWM duty cycle on that screen. I don’t know whether your phone needs to be rooted for this method to work.
No matter how you set it, it is a temporary change and will be reset next time the screen brightness changes, or if you turn your phone screen off and back on.
Does anyone know of an app that does this? There are plenty of auto brightness apps, and some brightness apps that require root, but I don’t know of any that set both the brightness and the duty cycle. I have some shell commands set up in Tasker, but it’s not very convenient. I could try creating a widget using Tasker, but I may just try writing my own app.
The roms are under a different model name search google for roms in the alcatel one touch pop line and many will work
So apparently the 1 III suffers from the same issues as its Sony Predecessors... The Flashlight is very bright when you use it as camera flash, but when you turn on the flashlight, its artifically throttled to idk, prevent overheating?
So for the older Xperias there were ways to modify flashlight configs and librarys. However, I havent found a way to edit the current parameter for the flashlight on the 1 III. For the 5 II the GodlyTorch App seemed to work, according to a report in https://forum.xda-developers.com/t/...ness-fix-torch-light-not-photo-flash.4203293/, but that doesnt want to work on my 1 III (I have Root)
Now the question: Can someone find the parameters to increase Flashlight LED Current via Magisk Module, XPosed/LSPosed Module or manual edit? I'd be even willing to donate to a kind developer who builds a usable flashlight mod for the 1 III.
Thanks in advance.
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
MK73DS said:
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
Click to expand...
Click to collapse
Thanks for this info, working fine for me!
I played a bit around with this and tested the brightness values with 150; working fine in terms of short term heat development.
Edit 2: After a few days I start to notice a very slight discoloration of the diffusor with a value of 150. Its not affecting anything and barely visible, but I'd recommend to go lower than 150, because I suspect the LED may get too warm for the diffusor. I changed the guide to use 30 for now (which equals double the brightness compared to stock), please test your values for yourself, its probably better to not exaggerate it.
Make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible for side effects resulting from the mod.
With Terminal Shortcut Pro and assigned Root Priviliges I made myself a Home Screen Icon that will boost the values for me in the current "Torch session" once the LED is turned on before. Other terminal emulator apps will work too.
In the Shortcut I set Run with Root and used the following command
Code:
echo 30 >> /sys/class/leds/led:torch_0/brightness && echo 30 >> /sys/class/leds/led:torch_3/brightness
Basically just a command that writes the 30 brightness value to the 2 files.
If someone can find a terminal command that turns on the flash in the first place, we could combine the commands to potentially make a simple but working replacement quick settings for the torch.
Edit: Thanks to the XDA Community and a Tool I was able to recreate the Torch experience with a Quick setting
You need https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings
You have to buy the premium in app purchase for 1,29€ to unlock Root Command Running. Then you configure your quick setting (choose the Advanced -> Root Command under Preset) and paste the following script (credits to https://forum.xda-developers.com/t/increasing-torch-power-with-root.3637773/post-73098701, modified by me for 1 III)
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 30 > /sys/class/leds/led:torch_0/brightness
echo 30 > /sys/class/leds/led:torch_3/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_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Once again, make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible side effects resulting from the mod.
Then you get rename the toggle, give it a nice Torch Icon and set the color to grey. It will function like the normal quick setting: Tap once, it turns on, Tap again, turns off. Even works locked.
Good luck and best regards.
If you want to use the Google Assistant Button as a torch toggle and also have Quick Settings Toggle (sadly its always toggled on) i found an app that can do both.
You need:
LSposed/Xposed
Root Shell access (adb shell)
Xposed Edge pro
Busybox for Android NDK (Magisk Module)
XperiaGAButtonRemap (Magisk Module)
Open a cmd or powershell
execute adb shell
execute su
accept root permissions on your phone
execute vi /bin/torch
press the key i
paste the script:
einhuman197 said:
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 150 > /sys/class/leds/led:torch_0/brightness
echo 150 > /sys/class/leds/led:torch_3/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_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Click to expand...
Click to collapse
press ESC
type :wq and press ENTER
execute chmod +x /bin/torch
Now you can execute /bin/torch as root and it will toggle the torch with higher brightness values.
In Xposed Edge enable "Keys" toggle and open it. Tap on "+ Add" at the bottom, press the Google Assistant Button, it should be recognized as "KEYCODE_PROG_BLUE", then set the action of either click/double click/long press (whatever you prefer as the torch toggle) to execute a Shell command, enter /bin/torch in the input field and enable the "Root access" toggle.
If you want, you can also set other custom things to the Google Assistant button for the other 2 states.
For the quicksettings menu tap on "Quick settings tiles" in the main menu of Xposed Edge and enable the first tile and open the settings for that tile. Set the action, again, to a shell command, input /bin/torch and enable Root Access. You can set the label to "Torch" and choose the Torch icon found in "Built-in icons". As i already said, the toggle will always be turned on for some reason. It just executes a shell command after all.
Good luck
Amazing, thank you everyone.
However, please let me insist that this may damage your phone if you put values too high... trust me. I accidentally put a brightness of 350 instead of 150 while trying the script in a terminal, and a few seconds were enough for the plastic underneath the glass to melt... Thankfully, it is still transparent so I can still use my flashlight, but no doubt it could have done a lot more damage if I let it run for longer. So please, use this with a lot of care (and double check what you write).
That's why in lots of countries, rooting voids your (hardware) warranty, you can do physical damage to your device so again, please be careful. Thankfully, this plastic bit and even the LED underneath are easily replaceable (the plastic bit is separated from the rear glass and the LED is on a separate ribbon cable). However, there don't seem to be a lot of OEM replacement parts for this phone yet.
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
jaseman said:
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
Click to expand...
Click to collapse
Sony could definitely improve it. But it seems like they had a history for compareably dim Flashlights.
I edited my explanation post to adapt lower brightness, because 150 as value starts to slightly discolor my diffusor, so I suspect we should run it lower.
MK73DS said:
太棒了，谢谢大家。
但是，请让我坚持，如果您将值设置为高，这可能会损坏您的。......我相信在终端中尝试手机时，我不小心将恢复设置为 350 而不是 150 ，几秒钟就可以让玻璃下面的恢复正常……幸好还是可以的，所以我可以使用我的手电筒，但有疑问，如果我能运行更长时间，它会请小心使用它（并仔细检查你写的内容）。
这就是为什么在国家/地区，root 导致您的许多（硬件）故障，您可能会再次对您的设备造成物理损坏，请小心。值得庆幸的是，塑料钻头甚至下面的 LED 都可以轻松更换（塑料钻头与后玻璃分离，LED 还位于单独的带状电缆上）。
Click to expand...
Click to collapse
darken5404 said:
Click to expand...
Click to collapse
You can't say I didn't warn you!
Indeed flashlight in mark 3 and older xperias is very bad.
I compared it to an iPhone and it's like day and night. Many aspects xperia brand is suffering like front camera, flashlight, no 21:9 pics, missing 4k 60fps recording in main app with stabilization, poor screen brightness, insufficient battery capacity, no any cooling system (especially at this price there should be vapor chamber or any other advanced cooling and not throttling cpu as a solution...), Not to mention regular software apps like Album, email and others :/
MK73DS said:
You can't say I didn't warn you!
Click to expand...
Click to collapse
I got it fixed through sony aftermarket and has ip68,fixed the screen for me by the way
On android 12 after rebooting the function stops working.
So I got to the area of the phone you guys specified, but as of today, the default values are WAY different that what yall found. Let me take a few screen shots
Here is the systems default peramitors. Any idea why they are so different?
Edit- Okay, so extra piece to the puzzle. When torch is off, the brightness file is 0, but when it is on the file is set to 15.
editing the file while the torch is on does nothing.
Edit 2 - Just wanted to note that for those who just want a demonstration of the changes possible, the fallowing app will do just that
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
this app needs root. Run it as a HTC 10 and it works just fine. However, I would like to recommend NOT going over the half way point. its VERY bright and will probably kill your LED if you do. You have manual control over the brightness. You can add it as a shortcut in the drop down menu of your phone. simply use the standard torch button, and then click the godly torch button to activate whatever preset you gave it.
Edit 3 - setting the brightness in Godly Torch to 50% Intensity sets the brightness to 135. Given that we know damage starts to happen at 150, I set the brightness in Godly to 15% (under the "toggle Intensity" shown in the screen shot), which brings the brightness to a value of 45. Its easily double as bright. I would not recommend going past this point.
I would say by using godly torch as a HTC 10 worked...mind you I double checked the brightness by just hitting the quick toggle and then messing with godly torch. The lower setting is matching just turning on the quick toggle the higher setting is what I'm comfortable with, but idk how long I'm comfortable running it at that brightness.
BlazingKahn35 said:
On android 12 after rebooting the function stops working.
Click to expand...
Click to collapse
For those on stock who use the assistant button :
If it stops working after reboot, copy the binary file to somewhere safe on your sd card, then using XPosed edge just add a long press gesture to your assistant button that recopys the file from your sd card, then sets the permissions again (make sure to check run as root)
cp /sdcard/torch /bin/ | chmod +x /bin/torch