Related
Hi guys. Now, when we have root for 2.1, is there any chances for disable light sensor?
hugerth said:
Hi guys. Now, when we have root for 2.1, is there any chances for disable light sensor?
Click to expand...
Click to collapse
Good point. That or ..
Original Eclair dialer would make this phone much better..
Would be great to disable this damn light sensor. I don't understand why can't we disable it to the hell out??
The light sensor seams to be OAM apk, so maybe removing them would disable light sensor... I didn't try yet, so if someone try, let us know if it works.
Where is it?
I did a misstake : it's not OAM but OMA.
And i think to remember that there were 2 OMA apk in system/app folder
i have install "quick settings" and there is an option to turn on/off light sensor
I installed it but I don't manage to find the option
Maze_fr said:
I installed it but I don't manage to find the option
Click to expand...
Click to collapse
click to open the application
click menu button - settings
click on brightness (icon key)
sorry, i have my phone other language and i don´t know the exact words in english
Sure but auto brightness still works no matter how u turn it off. Its a bit annoying.
::SEx8+root+xRecovery+JiT+app2SD::
Yes ! great ! it worked ! thanks.
Doesn't work for me...
Sent from my E15i using Tapatalk
Disable Light Sensor
I made it. now here the instruction:
1- download attach
2 - unpack it
3 - copy to the phone /etc/
4 - chmod 777
5 - reboot the phone
Thats all, you don't see work of this sensor.
Ok, it works at 100%. But... Ekhm... brightness is just crazy now xd I think I prefered old settings ;p. I'll try it tommorow.
Thanks.
Sent from my E15i using Tapatalk
dviktor said:
I made it. now here the instruction:
1- download attach
2 - unpack it
3 - copy to the phone /etc/
4 - chmod 777
5 - reboot the phone
Thats all, you don't see work of this sensor.
Click to expand...
Click to collapse
This doesn't work for me... I have 2.1-update1, latest pre-rooted Chinese firmware...
When I try to run it from adb it says something about /sys/... directory - "directory nonexistent", that it couldn't be created...
It's working now, I did it from xRecovery
Thanks, it's great... and just like hugerth says, brightness is CRAZY!!!
new version of Light Sensor Disable
i made a new version. it's got a normal bright and decrease a power consumption (i hope)
Can you write a small description on those changes, what does what ?
i write it in my post
Hi, all.
Could someone enlighten me a bit, what exactly do the light sensor do, and what would be the advantage (and disadvantage) of turning it off?
Cheers.
The light sensor is what detects ambient light around the phone and automatically adjusts screen brightness to torch your eyes out.
My ERIS g-sensor has a tendency to get out of whack. What I mean is that if you leave autorotation on with the phone lying flat, the screen will often rotate 90 degrees as if you were holding it in a landscape position. If you download a level app, it will show level surfaces as not level. Any while several gps and level apps allow you to calibrate what level is, they do not affect the autorotation being off.
The g-sensor is easily calibrated on a stock sense rom in the settings menu. But AOSP and CM ROMs do not provide a calibration tool, and calibration is reset with every newly flashed ROM. So, for a long time, I just turned off autorotation.
I did find a fix, adapted from here (http://forum.xda-developers.com/showthread.php?t=803242), but simplified below.
What you need:
A CM or AOSP ROM. I've tested on Condemned Soul's CM7 ROM.
A Root File Manager App with Text Editor capability. I'm using ES File Explorer
GPS Status App or another level or sensor app
1. Open GPS Status App (or other sensor app). Lay the phone on a flat level-ish surface. Observe how far the "bubble" in the center of the compass is offset from "level" or the solid circle in the middle of the compass. You can numerically see what the Pitch (up-down) and Roll (left-right) offset are. When calibrated, these numbers read 0 and the bubble will lie on-center.
2. Press home button, then open your file explorer. Navigate to /data/misc and locate the AK8973Prms.txt file. You may want to make a backup of this file, in case anything goes wrong. Open the file in the text editor. Locate the following:
AOFFSET.x=0
AOFFSET.y=0
3. Adjust these values by increments of 1 (or -1) until the GPS app shows it is level. Here's how: To move level left, change AOFFSET.x=0 to AOFFSET.x=1 then save the file. Long-press home to select the GPS app and check for level. If not level, increase to AOFFSET.x=2, save, and check again. Repeat until roll is level, then modify AOFFSET.y=0 until pitch is level. My final values are x=4 and y=-4. I haven't tweaked the z value (that is vertical level or plumb) but you can calibrate the same way if you have a plumb surface (like a newish house door). I live in an old house - nothing is plumb!
4. Enjoy your calibrated G-Sensor.
In GPS Status, does menu->tools->"calibrate pitch and roll" help any? Maybe it just calibrates for the app itself and not system wide. I keep auto-rotate off most the time so I don't have much experience with the screen switching when it shouldn't.
MongooseHelix said:
In GPS Status, does menu->tools->"calibrate pitch and roll" help any? Maybe it just calibrates for the app itself and not system wide. I keep auto-rotate off most the time so I don't have much experience with the screen switching when it shouldn't.
Click to expand...
Click to collapse
Correct, the app just calibrates itself, not the system. I know, it's only a minor annoyance, but makes me happy...
Sent from my ERIS using XDA App
I wasn't trying to imply that you should turn off auto-rotate, was wanting to describe why I might have sounded like an idiot asking whether that tool did anything system wide lol. I can see it being more than an annoyance so I'm glad you found and shared a way to fix it.
No worries mgh! Lol
Sent from my ERIS using XDA App
Thanks for posting this, klob! There are times when auto-rotate does come in handy, but then there are times when I don't want it on. I'll try this and see if it helps me out.
snortman
Good luck!
Sent from my ERIS using XDA App
help required
klobkelosh said:
My ERIS g-sensor has a tendency to get out of whack. What I mean is that if you leave autorotation on with the phone lying flat, the screen will often rotate 90 degrees as if you were holding it in a landscape position. If you download a level app, it will show level surfaces as not level. Any while several gps and level apps allow you to calibrate what level is, they do not affect the autorotation being off.
The g-sensor is easily calibrated on a stock sense rom in the settings menu. But AOSP and CM ROMs do not provide a calibration tool, and calibration is reset with every newly flashed ROM. So, for a long time, I just turned off autorotation.
I did find a fix, adapted from here (http://forum.xda-developers.com/showthread.php?t=803242), but simplified below.
What you need:
A CM or AOSP ROM. I've tested on Condemned Soul's CM7 ROM.
A Root File Manager App with Text Editor capability. I'm using ES File Explorer
GPS Status App or another level or sensor app
1. Open GPS Status App (or other sensor app). Lay the phone on a flat level-ish surface. Observe how far the "bubble" in the center of the compass is offset from "level" or the solid circle in the middle of the compass. You can numerically see what the Pitch (up-down) and Roll (left-right) offset are. When calibrated, these numbers read 0 and the bubble will lie on-center.
2. Press home button, then open your file explorer. Navigate to /data/misc and locate the AK8973Prms.txt file. You may want to make a backup of this file, in case anything goes wrong. Open the file in the text editor. Locate the following:
AOFFSET.x=0
AOFFSET.y=0
3. Adjust these values by increments of 1 (or -1) until the GPS app shows it is level. Here's how: To move level left, change AOFFSET.x=0 to AOFFSET.x=1 then save the file. Long-press home to select the GPS app and check for level. If not level, increase to AOFFSET.x=2, save, and check again. Repeat until roll is level, then modify AOFFSET.y=0 until pitch is level. My final values are x=4 and y=-4. I haven't tweaked the z value (that is vertical level or plumb) but you can calibrate the same way if you have a plumb surface (like a newish house door). I live in an old house - nothing is plumb!
4. Enjoy your calibrated G-Sensor.
Click to expand...
Click to collapse
I am using micromax canvas nitro. My auto rotation stopped working the first time i installed twrp recovery. After making a backup and restoring the same rom my auto rotation started working. But now its not working in any condition. The file you listed AK8973Prms.txt cannot be found in the above directory...please help
surajsahijwani said:
I am using micromax canvas nitro. My auto rotation stopped working the first time i installed twrp recovery. After making a backup and restoring the same rom my auto rotation started working. But now its not working in any condition. The file you listed AK8973Prms.txt cannot be found in the above directory...please help
Click to expand...
Click to collapse
As far as I can tell, this fix only worked on early htc phones up to gingerbread. I was never able to duplicate this on ICS or later on other phones. Sorry, and good luck.
FXP045 released, http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
Current Issues (FXP045) and unofficial fixes
Hardware keyboard layout scrambled - Old keyboard file is no longer in this ROM but appearently just pasting the old stock file (attached) to /system/usr/keychars/ fixes the layout. The included keyboard changer app force closes.
LEDs under soft keys Return and Menu - Replace /system/etc/hw_config.sh with the attached file.
Screen flicker upon turning on - New issue in fxp045.
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
xutienan9520 said:
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
Click to expand...
Click to collapse
I believe these fixes will work on Ray but you should find the stock values from Ray ROM because there probably are some differences.
Basically, only one issue you're having can potentially be fixed using SK17i fixes and that is max brightness by applying the fix for screen flicker. If you can't get a hold of Ray's stock values, try SK17's stock ones, but do a backup in recovery just in case.
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
xutienan9520 said:
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
Click to expand...
Click to collapse
i'm editting these files on the phone. copy the file to sdcard to edit it, with any kind of text editor. i use edit function of Total Commander. then i copy over the original file in system with Root Explorer. backup original file to sdcard just in case.
dont know about Mac much, sorry.
root explorer is a paid app but i think ES file explorer has the required functionality
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
xutienan9520 said:
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
Click to expand...
Click to collapse
oh, i messed up the links. will be fixed in a moment =)
Per someones suggestion I've added modified files and instructions on how to replace the original CM ones.
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Thank you good Sir! Testing it later!
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Amazing job! I'm gonna test it out now in a super dark place to see if i can check whether it stays on when closed. =)
I'll be updating original post with results and updated files in a bit.
Edit: Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Nice to see process.
Now i need to find the button light for RAY
sulkie said:
Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Click to expand...
Click to collapse
I thought that
Okay, there is a binary called slidercounter that or something similar sets a system var. If you take your dev Tools app and look unter Configuration there it is mentioned:
hardKeyboardHidden=2 <- if closed
hardKeyboardHidden=1 <- if opened
We now just have to find out where it occurs and if not we make a background script that ech0 x (100) or 0 into the node depending on the state.
But there must be a system process watching this we could use.
Don't hide, I'll find you anyway
---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------
xutienan9520 said:
Nice to see process.
Now i need to find the button light for RAY
Click to expand...
Click to collapse
did you look, if in ray the nodes under /sys are similar to the pro mini?
you can test using adb shell or terminal app cat'ing the node to see what's in it and echo'ing a number to see what happens.
You meant progress, didn't you
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
PoedelPCS said:
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
Click to expand...
Click to collapse
not the most elegant solution but it'll do until the fix is in =)
good job though
If I had more time I would have searched where the system keeps the var keyboardHiddenState or how it was called and build a condition of if it's open and not bright enough to switch in on/off
But how I understood fxp the fact about the light seems to be enough to get this working ..I hope so
new issue:
km launcher disturbes camera module.
I use the KM Launcher to determine which keyboard to use in which state.
Portrait: swype
Landscape: thumb keyboard
Keyboard open: hardware keyboard
This is a very cool application that worked perfectly on my rooted stock. If it is active the cam works in the cam app, but not in many other apps that use the cam, e.g. barcoo barcode scanner. I have to disable KM Launcher before using these apps. Hope it'll be fixed automatically in the next release.
I just cannot guess why that happens.
Hey guys I still have the problem with the over sensitive lcd backlight, whenever I'm in a brightly lit room the backlight starts going crazy and sometimes goes so dark I can't see the screen, it then goes super bright.
It repeats this several times a day
I've tries the fix in this thread but it doesn't work
Could someone attach the fix to this thread? As I've tried the the fix using terminal emulator
Thanks
EDIT: it started doing this while I was writing this
Sulkie did append the script to the first post of the thread. Did you test it?
send from a fruit called mango using xda app.
I did it before but it didn't work, I found the reason it didn't work was because I didnr change the permissions.
Sorry I got confused
---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------
Its still going crazy, I followed the instructions properly though,
When I get home ill upload a video of it happening
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
khudko83 said:
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)
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