Database Users

[Q] newbie help

hi, ive tried cm, but it wont let me controll it from my keyboard, (aosp crash) and i rly want to use it stock, now im rooted, i can go back to stock, i can even have a launcher on it, as long as i can keep its stock purpose, to play my music and look awesome while doing it, but i cant get past the welcome screen, now, is there any way to bypass that?

meldalinn said:
hi, ive tried cm, but it wont let me controll it from my keyboard, (aosp crash) and i rly want to use it stock, now im rooted, i can go back to stock, i can even have a launcher on it, as long as i can keep its stock purpose, to play my music and look awesome while doing it, but i cant get past the welcome screen, now, is there any way to bypass that?
Click to expand...
Click to collapse
Not really. I'm thinking about how to make the ring dance using setting persist, but I'll have a lot to learn before then.

animal24 said:
Not really. I'm thinking about how to make the ring dance using setting persist, but I'll have a lot to learn before then.
Click to expand...
Click to collapse
nice, when u do, pls post a guide, i would rly love being able to use the leds, ure running cyan?

animal24 said:
Not really. I'm thinking about how to make the ring dance using setting persist, but I'll have a lot to learn before then.
Click to expand...
Click to collapse
Pro-tip: using setprop is really slow, IIRC. There is a program called avrlights that is used via a shell that allows you to change the ring faster with more granularity. If you're looking to get some dancing going on, avrlights is probably what you want (just know that it's kind of janky). On the other hand, if you just want to change the whole ring color, setprop will work, but it's still kinda slow.

mcsaucy said:
Pro-tip: using setprop is really slow, IIRC. There is a program called avrlights that is used via a shell that allows you to change the ring faster with more granularity. If you're looking to get some dancing going on, avrlights is probably what you want (just know that it's kind of janky). On the other hand, if you just want to change the whole ring color, setprop will work, but it's still kinda slow.
Click to expand...
Click to collapse
I like you already.
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
mcsaucy said:
Pro-tip: using setprop is really slow, IIRC. There is a program called avrlights that is used via a shell that allows you to change the ring faster with more granularity. If you're looking to get some dancing going on, avrlights is probably what you want (just know that it's kind of janky). On the other hand, if you just want to change the whole ring color, setprop will work, but it's still kinda slow.
Click to expand...
Click to collapse
Is this in the play store? I can't find it.

animal24 said:
I like you already.
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
Is this in the play store? I can't find it.
Click to expand...
Click to collapse
Happy to help out.
It's not in the Play Store. avrlights is not an Android app. It is a compiled binary that exists on CyanogenMod-enabled Q's.
Here's how it works:
Open the Terminal Emulator app
Type "su -" (without quotes) and press enter
Give Terminal Emulator root access when prompted
Type "avrlights <ARGUMENTS>" (without quotes and see the arguments section below) and press enter again
So, you only need to do steps 1 through 3 when you open up a Terminal Emulator session. After all, once you're at a root shell, you don't need to get a root shell again.
So, let's talk arguments. If you just run "avrlights", it should set your LEDs to the default color (whatever is stored in persist.sys.ringcolor). If you run "avrlights <COLOR>", you change the ring color. If you run "avrlights <COLOR1> <COLOR2> <COLOR3> <COLOR4> <COLOR5> ... <COLOR32>" you can change each LED to a color.
How does this work? Well, first things first. Let's talk about encoding color. Color for a RGB LED on the Q (we have 32 around the ring of the Q) is 24-bit, with 8 bits per channel. This is fairly common. The strength of each channel is represented by a value ranging between 0 and 255 in base 10, or 0x00 and 0xff in hexadecimal, where 0 (0x00) is completely off and 255 (0xff) is full force.
With me so far? You can make a lot of different colors by combining these 3 component colors. I'd recommend Googling for a RGB color wheel and playing around with one of those if you want to get a better grasp.
You can combine these primitive colors using pretty simple math to represent more complex colors. For example, solid yellow would be (r,g,b) -> (255, 255, 0). If you mash these 3 values together using (r * 256 * 256 + g * 256 + b) to get a single number for your color, you can now update your ring with avrlights! It would be really nice if you could just use hexadecimal to update avrlights (that way it's just 0xRRGGBB and you don't need to do math on the fly), which is why I included that feature in my rewrite. In the mean time, you can kind of update with hex. Just do the following: "avrlights $( printf '%d' 0xRRGGBB ) ..." The printf statement converts your hex to base 10 on the fly, making it an acceptable workaround.
TL;DR: open up Terminal Emulator and run `avrlights $( printf '%d' 0xRRGGBB )` where RR, GG, and BB are your component colors in hex. You can specify multiple colors in a single call. To do so, just add them to the list of arguments.

mcsaucy said:
Happy to help out.
It's not in the Play Store. avrlights is not an Android app. It is a compiled binary that exists on CyanogenMod-enabled Q's.
Here's how it works:
Open the Terminal Emulator app
Type "su -" (without quotes) and press enter
Give Terminal Emulator root access when prompted
Type "avrlights <ARGUMENTS>" (without quotes and see the arguments section below) and press enter again
So, you only need to do steps 1 through 3 when you open up a Terminal Emulator session. After all, once you're at a root shell, you don't need to get a root shell again.
So, let's talk arguments. If you just run "avrlights", it should set your LEDs to the default color (whatever is stored in persist.sys.ringcolor). If you run "avrlights <COLOR>", you change the ring color. If you run "avrlights <COLOR1> <COLOR2> <COLOR3> <COLOR4> <COLOR5> ... <COLOR32>" you can change each LED to a color.
How does this work? Well, first things first. Let's talk about encoding color. Color for a RGB LED on the Q (we have 32 around the ring of the Q) is 24-bit, with 8 bits per channel. This is fairly common. The strength of each channel is represented by a value ranging between 0 and 255 in base 10, or 0x00 and 0xff in hexadecimal, where 0 (0x00) is completely off and 255 (0xff) is full force.
With me so far? You can make a lot of different colors by combining these 3 component colors. I'd recommend Googling for a RGB color wheel and playing around with one of those if you want to get a better grasp.
You can combine these primitive colors using pretty simple math to represent more complex colors. For example, solid yellow would be (r,g,b) -> (255, 255, 0). If you mash these 3 values together using (r * 256 * 256 + g * 256 + b) to get a single number for your color, you can now update your ring with avrlights! It would be really nice if you could just use hexadecimal to update avrlights (that way it's just 0xRRGGBB and you don't need to do math on the fly), which is why I included that feature in my rewrite. In the mean time, you can kind of update with hex. Just do the following: "avrlights $( printf '%d' 0xRRGGBB ) ..." The printf statement converts your hex to base 10 on the fly, making it an acceptable workaround.
TL;DR: open up Terminal Emulator and run `avrlights $( printf '%d' 0xRRGGBB )` where RR, GG, and BB are your component colors in hex. You can specify multiple colors in a single call. To do so, just add them to the list of arguments.
Click to expand...
Click to collapse
So to set the mute color we still use setprop i imagine.

animal24 said:
So to set the mute color we still use setprop i imagine.
Click to expand...
Click to collapse
I believe so. There is some weird stuff that can go down due to the use of uninitialized memory, IIRC. Looking at the code, the mute LED looks to be set to the first color you give it.
Code:
color = prepare_leds(colors[0]);
ioctl(fd,AVR_LED_SET_MUTE,&color);

[Q] Auto enable ultra power saving mode??? at %

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.

touchscreen calibration and some other (related?) things

Backstory (because context is always nice)
Before I got my ZenFone2 I was using a samsung galaxy s2 as my main phone.
It was a really nice phone and became even better after some small modifications such as attaching a bluetooth keyboard to it and converting the touchscreen to a touchpad (like those things on laptops). With a chroot linux installation it actually felt like a pocket computer. However it had rather low processing power and very little ram and a small screen with a low resolution. The zf2 with its good specs and x86_64 would be much better suited to be truly a pc in the pocket....
So I wanted to make the touchscreen on the zf2 behave like a touchpad.
According to this, I only need to change 1-2 lines in an .idc file.
This worked well on the sgs2 (filename:sec_touchscreen.idc) but on the zf2, there is no such file.
After looking through a bit of kernel code, I found out that the file should be called "ftxxxx_ts.idc".
After creating the file you can start to calibrate the behaviour of the touchscreen.
This might be helpful: https://source.android.com/devices/input/touch-devices.html
touchscreen --> touchpad
Here are the basic steps of making the touchscreen behave like a touchpad.
Simply run these commands in a root shell
Code:
echo "touch.deviceType = pointer" >> /system/usr/idc/ftxxxx_ts.idc
echo "touch.gestureMode = spots" >> /system/usr/idc/ftxxxx_ts.idc
echo "touch.orientationAware = 1 " >> /system/usr/idc/ftxxxx_ts.idc
chmod 544 /system/usr/idc/ftxxxx_ts.idc
chown 0:0 /system/usr/idc/ftxxxx_ts.idc
or add these three lines manually to the file (also create if it doesn't exist).
Code:
touch.deviceType = pointer
touch.gestureMode = spots
touch.orientationAware = 1
Make sure the permissions are correct (544 or rwrr).
ALSO IMPORTANT: Make sure that there are no mistakes in the code before running it (because I might have mistyped something....but I don't think so).
(Soft-)Reboot for the changes to take effect.
touchscreen <-- touchpad
To revert the changes, you can delete the file or change
Code:
touch.deviceType = pointer
to
Code:
touch.deviceType = touchscreen
You can also comment out the line.
Code:
#touch.deviceType = pointer
This should make it behave like a touchscreen again.
What next:
I still need to find a way to change between touchscreen and touchpad mode on the fly without doing the editing and rebooting.
Maybe an xposed module could do this, but I have not found one and I have no idea how to write one.
Therefore.....If anyone knows how to do this, please help.

Increasing torch power with root

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

DELETED - misread

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[BASH SCRIPT] Torch fix for pie GSIs

so, I was googling around a bit, a few days ago, and found out you can control the torch (and other leds) from the command line, or a bash script.
Prerequisites
root (magisk or superSU)
FX file manager or Termux
Text editor
Instructions
Create a file in a directory of your choice with a '.sh' extension
Add the following code to the file:
Code:
su -c 'echo 255 > /sys/class/leds/torch/brightness'
Run the shell script in termux (cd to the directory and run it) or run it using FX, it will ask for root access if you haven't already granted it
Your torch is now on!
To turn it off create another file with
Code:
su -c 'echo 0 > /sys/class/leds/torch/brightness'
in it
Tested on an Honor 9 and P10+
If you have dual tone flash, yo may find different values cause either led to come on, for me, '255' is the yellow flash and '1' is the white flash
For a bit more messing around, cd to the '/sys/class/leds' directory, you will see a few more directories for other LEDs on your device, controlling them is exactly the same as the torch!

Works for me, thanks a bunch dude
EDIT: on honor 7x/Huawei mate se

Thank you so much for this but I found in my own experience, and from comments I saw where this has been shared, that a bash script perhaps wasn't the most effective to have to run each time so I thought of implementing this to Tasker, create a "pseudo toggle" and allocate it to a quick setting tile. The algorithm is:
Code:
If flashlightStatus = TRUE then
Run shell command: su -c 'echo 0 /sys/class/leds/torch/brightness'
Set variable flashlightStatus to FALSE
Else
Run shell command: su -c 'echo 3 /sys/class/leds/torch/brightness'
Set variable flashlightStatus to TRUE
End If
I set it up this way because if you've never set the variable before (or if it clears on reboot or something) then it won't equal true and would still enable. Also, when I set the brightness to 255 the torch had a slight yellow tint so upon further reading, despite that 255 should be full brightness, apparently max brightness is 3 and is a white light (this seems to disable automatically after around 750ms however). Hope this will help those who are still without a torch on treble GSIs.
P.S. I also set up a quick profile that if the flashlight status variable = true then to wait 750ms and check if still true then change to false and turn off the torch; this would reset to compensate for the OS turning the torch off automatically but Tasker still thinking it was on. I'm not sure how necessary this is or whether it's overkill or not.

beejkitsune said:
Thank you so much for this but I found in my own experience, and from comments I saw where this has been shared, that a bash script perhaps wasn't the most effective to have to run each time so I thought of implementing this to Tasker, create a "pseudo toggle" and allocate it to a quick setting tile. The algorithm is:
Code:
If flashlightStatus = TRUE then
Run shell command: su -c 'echo 0 /sys/class/leds/torch/brightness'
Set variable flashlightStatus to FALSE
Else
Run shell command: su -c 'echo 3 /sys/class/leds/torch/brightness'
Set variable flashlightStatus to TRUE
End If
I set it up this way because if you've never set the variable before (or if it clears on reboot or something) then it won't equal true and would still enable. Also, when I set the brightness to 255 the torch had a slight yellow tint so upon further reading, despite that 255 should be full brightness, apparently max brightness is 3 and is a white light (this seems to disable automatically after around 750ms however). Hope this will help those who are still without a torch on treble GSIs.
P.S. I also set up a quick profile that if the flashlight status variable = true then to wait 750ms and check if still true then change to false and turn off the torch; this would reset to compensate for the OS turning the torch off automatically but Tasker still thinking it was on. I'm not sure how necessary this is or whether it's overkill or not.
Click to expand...
Click to collapse
mind if i improve this?
Code:
su -c 'if grep -q 1 /sys/class/leds/torch/brightness; then echo 0 > /sys/class/leds/torch/brightness; else echo 1 > /sys/class/leds/torch/brightness; fi'
-- obviously you can change the 1 to whatever you want
that is the code i'm using, prevents the use of an unnecessary variable, so is faster, and will use less resources, plus its pretty much fail safe, since it reads the current state of the torch to determine if its on or off, so if something else sets it to a state it still works, if something else set you variable externally then the torch becomes messed up until a reboot.
plus, im assuming that variable is a tasker thing? not everyone will use tasker, so eliminating the variable all together makes it work on any app that can add custom quick settings tiles

ambitiousButRubbish said:
mind if i improve this?
Code:
su -c 'if grep -q 1 /sys/class/leds/torch/brightness; then echo 0 > /sys/class/leds/torch/brightness; else echo 1 > /sys/class/leds/torch/brightness; fi'
-- obviously you can change the 1 to whatever you want
that is the code i'm using, prevents the use of an unnecessary variable, so is faster, and will use less resources, plus its pretty much fail safe, since it reads the current state of the torch to determine if its on or off, so if something else sets it to a state it still works, if something else set you variable externally then the torch becomes messed up until a reboot.
plus, im assuming that variable is a tasker thing? not everyone will use tasker, so eliminating the variable all together makes it work on any app that can add custom quick settings tiles
Click to expand...
Click to collapse
Yes, the variable is a Tasker thing so I'm glad there is a solution that wouldn't rely on it. Thanks for the upgrade and I've already switched out my Tasker profile for this. Doesn't seem any quicker or anything but more simple!