Related
01/26/09 - This is just a minor update to fix some issues and add a couple small features.
Feel free to give comments or ask questions.
Thanks!
This program is a touch driver to handle the touchscreen presses and vibration. A settings program exists to configure how the vibration works.
Since this is a touch driver, there is no program you need to run to start it.
It has been tested on an HTC Touch and HTC Touch Pro for several days with several stability issues corrected. I am only releasing this now that I feel comfortable that you will experience no major issues. However, I cannot guarantee that it will work flawless for you. I cannot be held responsible for any loss of data or time you may experience while using this.
If you are experiencing problems after installation, please let me know so I can fix these issues.
Features
Global enable/disable option
Vibrate on touch/release
Variable duration of vibrate
Disable during Phone Call option
Disable when device is silent
Disable when device is locked
Disable when stylus is out (for devices that support this option)
Enabled for On-Screen Keyboard only (Temporary option until full include/exclude list is incorporated)
Settings Program->Settings->System->TouchResponse Settings
AppToDate support
Coming Soon
Include/Exclude list for vibration
Different vibration patterns
Resolve any software conflicts
Vibration tweaks
Sound on touch
Vibrate on hardware button press
Multi-language support in Settings program
I'm open to suggestions...
Known Issues
May or may not play well with touchflo/ftouchsl. If TouchResponse isn't working for you, try disabling those if they are enabled.
Disable when device is silent may not work on some devices. Let me know what kind of device you have if this is the case for you.
Donate
This is a free program and I plan on keeping it that way. If you enjoy using it and would like to support its development, please consider donating by clicking here:
Donate $ | Donate €
Change Log
.3.2 (01/26/09) - Minor update
- Option to disable vibration when device is locked
- AppToDate now supported - Download AppToDate to be informed of the latest updates
- Fixed issue when SIP Only didn't work as expected in landscape mode
- Fixed issue when Stylus Out still resulted in vibration when that option was set.
.3.1 (01/14/09) - Minor update
- Should properly upgrade when built into a custom rom
.3 (01/13/09) - More features
- Option to vibrate on release of touch
- Option to disable vibration when stylus is out
- Option for vibration to only be enabled for on-screen keyboard
- Better auto-detection of device model/vibrate id
.2.2 (11/27/08) - More Minor Updates
- Can increment the duration by one instead of five now
- The chance for a longer than usual vibration should be reduced if not eliminated altogether
- Disable while silent option should work a little better now
- Settings program allows for more Vibrate IDs in the Advanced tab
.2.1 (11/26/08) - Minor Update
- Windows Mobile 5 is now supported
.2 (11/26/08)
- Attempt to resolve suspend issues with certain phones - Let me know
- Disable while silent option added - may not work perfect
.1 (11/24/08)
- Initial Release
Questions and Answers
Q. How to I change the settings?
A. Start->Settings->System->TouchResponse Settings
Q. Why do I not see the settings program?
A. For some phones, the settings program does not appear in the control panel. Until I figure out a fix, you can run the program by going to \windows\TouchResponseSettings.cpl
Q. Why is it not vibrating when I touch the screen?
A. Go to the Device tab in TouchResponse Settings. It will display information about your device. If it says to select your vibrate id then find the one that causes the vibrate to work. Send me a PM with the name of your device model along with the vibrate id that works for you and I will incorporate that into future releases.
Q. Will this drain my battery life?
A. I don't have any statistics to show the before and after battery usage. However, I personally have not experienced any significant increase in battery usage. It all depends on how long the vibrate duration is and how often you touch the screen.
Q. Why does the vibrate last longer than it's supposed to sometimes?
A. This should hopefully be resolved as of version .02.2. If you experience this after this version, please let me know when it happens and how often.
Q. Why is the vibration always the same duration no matter what the settings are set at?
A. Use a registry editor to go to HKEY_LOCAL_MACHINE>Software>OEM>VIB and set STRENGTH_LOW to 0. Thanks to agdaniels for pointing this out.
Please don't post this cab on any other site. Let's keep all discussion here. I appreciate your cooperation.
Thank you for your support!
Ill try it and let ya know how it compares
Nice idea, thanks for sharing.
I read about a phone (I think it was LG Incite?) where some people complained about vibrating even when entering text with the soft-keyboard.
Could you give us an option to dis-/enable vibrating when entering text ? Maybe there´s an event you can use when the soft-keyboard flips up...dunno
regards,
Martin
m.schmidler said:
Could you give us an option to dis-/enable vibrating when entering text ? Maybe there´s an event you can use when the soft-keyboard flips up...dunno
Click to expand...
Click to collapse
Since the driver has first crack at the touch event, I should be able to determine which window is being touched and either vibrate/not-vibrate depending on how it's configured. For example, I can see that the SIP is being touched and not vibrate. I'll add that to the list, Thanks!
Just as Martin said.
When typng on the on screen keyboard. Vibrate on every button of the keyboard we pressing. That would be awesome.
Gonna test this on the X1i
It works great on my HTC touch PRO.
Yea Man !!
I love this Apps !!!
Thanks so much
all feature Works like a charm in my Kaiser (HTC TyTN II)
Well I guess I will put my suggestion here as I did with the other 2 programs like it. Would you consider creating a setting to were it is only active on SIP Keyboard AND when SIP keyboard is active I have choice between a vibration or a sound or both?
I know I can get a sound by going to the general settings of winmo but when it is on it makes a noise for all screen taps...annoying!!
CuriousG
curious george said:
Would you consider creating a setting to were it is only active on SIP Keyboard AND when SIP keyboard is active I have choice between a vibration or a sound or both?
Click to expand...
Click to collapse
Since this is a similar comment among everyone I will focus on this next. Thanks everyone for your feedback!
how about different types and lengths of viberations like the old motos used to have? dash-dash-dash-buzzz haha
maybe different intensities if possible?
I've always wanted 'heptic feedback' on my KS20 but non works for me. I've tried Heptick Feedback, Vibration Feedback and now TouchResponse, none work for KS20. Duh....
Can these options be added?
1. Not to vibrate when on silent?
2. Change buzz length (make it shorter/less intense)
3. An "use only when SIP activated" option.
richabi said:
how about different types and lengths of viberations like the old motos used to have? dash-dash-dash-buzzz haha
maybe different intensities if possible?
Click to expand...
Click to collapse
This is something I've been wanting to experiment with. I'll add that to my list, Thanks!
stutzedward said:
I've always wanted 'heptic feedback' on my KS20 but non works for me. I've tried Heptick Feedback, Vibration Feedback and now TouchResponse, none work for KS20. Duh....
Click to expand...
Click to collapse
You may have tried something similar with the other programs you have tried, but you can try changing the Led Id in the Settings program under the Advanced tab. Be sure to press ok to make the settings to into effect. Hopefully it is just a case where the KS20 doesn't use the default Led Id for vibrate.
derekwilkinson said:
Can these options be added?
1. Not to vibrate when on silent?
2. Change buzz length (make it shorter/less intense)
3. An "use only when SIP activated" option.
Click to expand...
Click to collapse
1. Yes, this is something I want to add! It's sometimes hard to go unnoticed when I use my phone in meetings at work when the vibration is loud.
2. Did you see the Settings program in the System tab of the "Control Panel"? Or do you mean a something like a longer buzz but less intense?
2. I'm going to be focusing on that with an include/exclude option next.
Thanks for your feedback!
Snailslug said:
You may have tried something similar with the other programs you have tried, but you can try changing the Led Id in the Settings program under the Advanced tab. Be sure to press ok to make the settings to into effect. Hopefully it is just a case where the KS20 doesn't use the default Led Id for vibrate.
Click to expand...
Click to collapse
Hey hey, it works for KS20 for the first time!!!!
I set the LED from 0 to 3 and hey, 3 works.
0 - LED displays green
1 - LED displays red
2 - LED displays blue
3 - it worked!
Thank you soo much! I gotta spread this on the KS20 thread because a lot of KS20 users are wanting this like me. I'll link them here.
very good work.
i have mine set to 25ms and the vibrate is a perfect length and silentness.
i agree on only sip active and/or blacklist
Just want to echo what's already said. What most ideally want is for vibration to be active ONLY on keyboard when text entering and to be as brief a buzz as possible. Some owners type very fast and we want the buzz to keep up and not still lag on the previous tap while tapping on the next key. It has to be super quick and not miss a key press when typing quickly. Thanks!
Ok, found the settings app, my bad
The other two requests would be awesome if they were to be fulfilled!
whats the difference between this program and this one : http://forum.xda-developers.com/showthread.php?t=425063 ??
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
Dear all,
Does anyone here know how to use Tasker app to auto enable and disable the always on display (AOD) setting in a specific time?
I noticed that enabling AOD consumes lot of battery, the battery drained 15-20% when my phone was idle overnight from 12am-7am. After I turn off the AOD, the battery drains only 5% overnight.
I'm thinking to use Tasker to disable the AOD when I'm sleeping to reserve the battery, and turn it back on after 8am. Unfortunately I couldn't find anything in the Tasker app that allows me to do so. But I'm able to do this to my previous Samsung Galaxy s7 edge. Maybe I missed out something when I tried to do that for my LG G5?
Is there anything in the Secure Settings app that might help with this? Worth investigating - haven't rooted yet (just whilst I'm getting used to phone and working out pros and cons) so can't check for you.
For what it's worth I just turn phone over which switches off AOD, easy to turn back to check time in dark...
Yeah I didn't notice that my AOD would turn off when I turned it over till later and thought that was a smart implementation for it. Seems very intuitive.
I'll revive this thread, as I'm looking for a tasker solution too. Is there any way I can disable the AOD via Tasker? I've a H850, stock nougat, rooted.
Try this method:
https://www.reddit.com/r/GalaxyS7/comments/4knout/always_on_screen_only_while_charging/
But replace "aod_mode" to "enable_ext_display_on_lcd_off"
I may be a bit late to the party, but you really don't need the paid version of secure settings app to toggle this setting on Samsung. Just run the following shell commands from tasker (make sure you check the "use root" box):
To enable:
Code:
settings put system aod_mode 1
To disable:
Code:
settings put system aod_mode 0
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
settings - display- blue light filter - custom schedule
vivilxw said:
settings - display- blue light filter - custom schedule
Click to expand...
Click to collapse
Blue Light filter is disabled and schedule is disabled as well. I've tried turning ON the blue light filter when the issue happens and it actually kicks in on top of the other issue and makes it even MORE yellow.
Seems unrelated to that.
Have you checked the sunset to sunrise toggle..?
Anyone having this blue light issue...blue light is enabled. When I turn on phone from sleep mode it takes like a second to switch to blue. Very weird
Sent from my SM-G965U1 using Tapatalk
zeebone said:
snip.
Click to expand...
Click to collapse
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
(ORIGINAL, not needed, left for posterity)
This needs more attention. I know EXACTLY what this is. You came from a more recent Android device that uses Google's own "night mode" settings. I know, because I did too. I came from the Razer Phone and had night mode enabled on that on schedule. After my screen turned a real dank orange color at night, I started looking for the setting and discovered Samsung's "Blue Filter" setting and that enabling it made the orange color even more dank. So I immediately knew that the setting must have carried over when I logged into my google account and carried over my settings.
I have a workaround, but it is just that, it's not a permanent fix and I'm still trying to figure out how to fix it permanently. You need to install System UI tuner from the playstore. Follow the instructions to make the app work by granting permissions using ADB while connected to a PC. This is not root and will not void your warranty as such. From here, you can either just disable "Night Mode" under the miscellaneous tab or you can go to the playstore and install "Nougat / Oreo Quick Settings" which will allow you to add the toggle for "Night Mode" to your quick settings pull down bar. Unfortunately, you have to do this every night to get rid of the ugly orange color.
I've tried disabling the setting on my Razer and syncing everything in my google account from that phone, then restarting my galaxy and hoping that the settings would transfer over, but it hasn't worked. My fear is that I will have to factory reset the Galaxy, go back to Razer, toggle the night mode on and back off. Sync settings, then sign back into my galaxy and hopefully the settings will not come back this time. I just haven't because I don't want to set EVERYTHING back up again, ugh.
If anyone is aware of how to disable the "Night Mode" schedule feature in a different way without factory resetting the device, please let me know. Thanks!
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
cawith said:
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
Click to expand...
Click to collapse
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
lessthanzach said:
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
Click to expand...
Click to collapse
Wish I had waited a little bit longer and had done this. I ended up backing everything up to my SD Card using Smart Switch and then wiping and rebuilding the phone yesterday afternoon. However, I didn't choose to restore from Google and only from Smart Switch, so the night light setting didn't end up carrying over again.
Good to know I wasn't crazy and that my phone wasn't defective.
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
I was all ready to get adb working and use the above workaround, and / or install nova launcher and fix this issue but THIS WORKED.
THANK YOU it has been bugging me for WEEKS.
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
You are amazing! It was the Google play books settings.
Thank you so much! It just started happening last week so I knew that it didn't come from my smart switch settings. Google play books was on night light settings from 10p-6a. I can see my phone again at night without my screen being yellow or without having to restart my phone. Thank you so much!!! I NEVER would've looked there.
Works like magic on my S7. Thanks a lot!
Perfect!
This fixed my problem, so thank you!
Google play book... who would have guessed..
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
zeebone said:
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
Click to expand...
Click to collapse
You might have your blue light filter turned on to a specific time. Mine is set to come on at 6 pm and go off at 6 am. Check that in settings.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Did you tripped your knox warranty, when using this ??..... I want to disable night mode on my note 9.....did adb trigger knox ??? Please advice sir... And thank you
Click to expand...
Click to collapse
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Buddy ur basically a lifesaver. Note 10+ fixed too, can confirm!
Buddy the workaround just saved me at least one trip to SES which is like 30 mins away from my house in Long Island, saved me from erasing the phone and restore it which would definitely be a nightmare and also u just saved my one big annoyance with this phone for the first week of usage!! U are the man!!
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
Vinay_sandy said:
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Click to expand...
Click to collapse
I tried it, both options switched off.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Click to expand...
Click to collapse
Huge thanks as you saved me from factory resetting my new Mi 9 Lite. That's why I love the internet.
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