Related
Guys, im the developer of Power Switch, an app that switches off your tablet's screen when you shut the case.
The main thread can be found here:
http://forum.xda-developers.com/showthread.php?t=1277712
Ive had reports of problems with the tab's light sensor, so would appreciate some debugging feedback.
You can use the lite version to test, it has all the features, but just wont save as much juice.
Thanks in advance. Feel free to reply here or in the main thread, i read both regularly!
Many thanks!, Looks very interesting, will try it out and see how it does with my Tab.
Let me know if the light sensor work properly please!
Got Pro version on my phone, works great.
Will try it on my tab soon.
I'll check it out when i get home.
Works great on my tab too. Thanks mate.
Edit: I noticed on my phone after testing it on and off a few times, the light sensor stopped working. But after rebooting, I havent seen the problem since.
And I've yet to see a problem on my tab.
So the light sensor works? Can you log some sensitivity settings for me so i can fine tune it...
ftgg99 said:
So the light sensor works? Can you log some sensitivity settings for me so i can fine tune it...
Click to expand...
Click to collapse
Like in different lighting settings? Like dimming the lights in the room? Or using different Sensitivity %s and closing the case?
Or all of the above?
Oh and after some extensive use on my DroidX, I've been having some problems. It turns off while I'm using the phone even in very lighted surroundings.
---------- Post added at 09:38 AM ---------- Previous post was at 09:20 AM ----------
I'm at work right now but I tried a few things.
I'm using a Belkin Folio case and i tested to see how low i could set the % for it to read when the case was closed.
Anything under 10% didn't work (even when i completely covered the light sensor with my finger)
On 100%, even a shadow over the sensor would trigger it.
I'll try a few different lighting instances when I get home.
Thats cool, thanks!
ftgg99 said:
Thats cool, thanks!
Click to expand...
Click to collapse
Sure thing, bud.
Still having issues with it on my DroidX. I've been trying different things but I dont think its user error.
You should be using the proximity sensor, not the light sensor for the phone!
ftgg99 said:
You should be using the proximity sensor, not the light sensor for the phone!
Click to expand...
Click to collapse
Oh well okay haha.
Its much more efficient...
Actually...to be honest, I dont even need it on my phone because its a habit of mine to hit the power button as im setting it down or putting it in my pocket.
I do love it on my tab though. Makes it easier just being able to close my case instead of trying to find the power button lol.
Can't remove this app from my tab! Help please
Sent from my GT-P7500 using xda premium
Disable admin permissions or click the uninstall button. Man, som people...
ftgg99 said:
Disable admin permissions or click the uninstall button. Man, som people...
Click to expand...
Click to collapse
Haha I know right...Don't see why he would want to uninstall it tho
The best ones are the Oles that leave market reviews claiming its "some kind of scam"...
Could you help me how to configure it n make it work? Mine seem not work. Duno how. Im using pro
Sent from my GT-P7500 using XDA Premium App
joseph168 said:
Could you help me how to configure it n make it work? Mine seem not work. Duno how. Im using pro
Sent from my GT-P7500 using XDA Premium App
Click to expand...
Click to collapse
Do you have "Enable Power Switch" Checked?
EDIT: If you're using a tablet with a case that covers the screen when you close it, here's what you need...
1. Check "Enable Power Switch"
2. Check "Admin Permissions" (this gives the app permission to lock your screen or turn the tablet off)
3. Check "Enable Sensors"
4. Check "Use Light Sensors" (I recommend 10-20% Sensitivity)
5. Set up your Confirmation and Activation Delay.
---Activation Delay is how long it takes for the device to read if the case is closed or not. (If you set it to 0 seconds, your screen will cut off even if you simply brush something up against the light sensor on accident) I keep mine at 3 seconds.
---Confirmation Delay starts after you Activation Delay ends. It is a confirmation dialogue box that asks what you want to do. Once the timer for it runs out, it will lock your screen/turn the screen off. (I keep mine at 3 seconds for this as well but you might want it longer)
To recap...Set Activation Delay for how long you want the device to wait before it makes a decision if it should turn off your screen or not. Set Confirmation Delay for how long you want it to wait after the Activation Delay ends to actually turn off the screen.
((If you don't have a case that covers the screen and you want it to turn off when you put your tab upside down, replace step 3 with *Check "Acceleration Sensor"* And make sure you Uncheck "Use Light Sensor"))
Is there a way to adjust the light sensor to respond to the external light quicker than it is currently configured to? I find the stock settings to be pretty slow. I am running ICS Alpha2 Dagr8 Rom.
Its a build prop tweak called "mot.prox.delay" I believe I know I misspelled it,I'm using my phone and at work....research for that,am sure that's what your looking for....like when you take your phone away from ear real quick and the keys should light up so you can hit a button right?.....
wish777 said:
Its a build prop tweak called "mot.prox.delay" I believe I know I misspelled it,I'm using my phone and at work....research for that,am sure that's what your looking for....like when you take your phone away from ear real quick and the keys should light up so you can hit a button right?.....
Click to expand...
Click to collapse
I think your are referring to proximity sensor. I was referring to the Sensor that adjust the screen's Iight brightness based on the outside brightness.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
supac said:
I think your are referring to proximity sensor. I was referring to the Sensor that adjust the screen's Iight brightness based on the outside brightness.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
true,, but there is only "one sensor" in the samsung that enables dark /light conditions, same one that works for phone ( while on call )...but your right..you can disable the >setting>Display>Auto adjust screen power setting
wish777 said:
true,, but there is only "one sensor" in the samsung that enables dark /light conditions, same one that works for phone ( while on call )...but your right..you can disable the >setting>Display>Auto adjust screen power setting
Click to expand...
Click to collapse
I see. I dont want to disable it, i just wanted it to react faster than it currently does
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
See if enabling wake on volume helps:
Settings > Display > Volume rocker wake
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
If you are using a screen protector, there is a known issue regarding placement. If the protector cutout is too close to the sensor, it will interfere with the proper operation of the sensor and blank out the screen too easily.
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
I don't have a screen protector. This solved it for me. Many thanks.
That said, the settings I'm using are a little weird. I have the Low set to 81, and it doesn't seem to matter what the High is set to (currently 100).
This fix works
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
this totally worked to fixed this same issue I have had. I used to have to go outside on a sunny day for my screen to come on while making a phone call. Once I used this app I was able to get it to come on in a dark room with hardly any light. I may at some point open her up and actually clean the inside of the sensor cover, but for now this worked like a charm.
Thanks for the tip.
One item to note, if you do decide to open your phone and clean the sensor windows, don't clean too aggressively or you will remove the tint from the backside of the glass. Just a tip.
I'm glad you guys have gotten your sensors working again.
I just had this problem today. Previously I never had issues with prox sensor, but just a couple days ago I did a complete wipe (data, cache, dalvik, system and internal SD card) and installed RC1 with a fresh install. The app mentioned above DID fix my issue however I know its a ghetto fix. Before running the app, the proximity sensor would work normally in good light, but not in low light. After running the app it works even in dark light which is great. However, I know its a weird fix. I can actually see the red proximity sensor during calls, when I couldn't previously. I'm glad I got it working, but I know there is something wrong still, and it's definitely ROM related as opposed to hardware because just 2 days earlier it worked fine before the clean install. Hmm..
Sent from my Incredible 4G LTE using xda app-developers app
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
If you don't know how to launch an activity, you can do the following:
Via ADB:
Code:
adb shell "am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences"
Via Terminal on your phone:
Code:
am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
I haven't done any more checking, but I'm guessing this is just a flag that could be set in sys/devices/blah... by init.d script on boot as well.
If you prefer a gui, there are plenty of launchers out there that can select an activity to start. I actually had it set up as a long-press pie on LMT while I was playing with it.
It seems (on my phone, at least), that the app wasn't as good at turning it back on, but you can just clear the app data/cache on "Content Adaptive Backlight Settings" in application manager, reboot, and you'll be back to stock behavior.
Sorry I didn't post this sooner. I've been too busy playing with the G2!
this doesn't work.
I've tried this weeks ago. simply telling the app to turn it off does nothing, as it's still on no matter what. deleting the app produces the same exact effect.
in the build prop, the line pointing to cabl is set to false. therefore it's really not even reading what the app is saying it seems.
I believe it's a kernel issue that can only be solved once we get a custom one.
again, this isn't a fix and doesn't turn it off at all sadly.
Sent from my VS980 4G using Tapatalk 4
https://www.youtube.com/watch?v=slwkFhpiYbs&feature=youtube_gdata_player this video was made when it was set unchecked and set to off.
Sent from my VS980 4G using Tapatalk 4
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Is this issue on all carrier versions?
I use auto-brightness and the annoyance I have is that it doesn't change brightness right away when entering different lighting environments. It either takes time or doesn't change at all until I uncheck/check the auto-brightness setting.
xdabbeb said:
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Click to expand...
Click to collapse
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
jayochs said:
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
xdabbeb said:
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
Click to expand...
Click to collapse
I believe the original Nexus 7 had this feature in the kernel too. However, in custom kernels you could use Trickster mod to toggle the feature off. I think the kernel devs had to expose the setting though, so maybe we'll get this taken care of if we can get a custom kernel.
Here are some build props for Qualcom devices that control the CABL
Code:
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
By adding / editing these lines in the build.prop you should be able to adjust as noted in the lines.
And yes, it is in the kernel.
Dont know why LG has an app for it?
Scott, I sent you a message on hangouts but in my build prop, i don't show a 1 for the cabl setting.. i show false... as if it's already turned off in the build prop. I changed it to true once and it didn't do anything. those two top settings seem to be what's in the app.. you can check a box to turn it on and off (the first line) and then you can set the degree to which it handles the cabl (second line.) I've messed with both in the app and it did absolutely nothing... does the kernel need to be changed as well?
Sent from my VS980 4G using Tapatalk 4
xdabbeb said:
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
Click to expand...
Click to collapse
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
we do want to bc it causes horrible screen flicker issues. you can be sitting on a pic and it doesn't know what to do so it flickers badly
Sent from my VS980 4G using Tapatalk 4
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
I did not know about the contrast ratio on these screens. Makes sense what you are saying.
However like Jay said it does not react smoothly or at appropriate times.
Some will need to edit the kernel code to fix this.
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
Yep. What @jayochs and @scrosler said. What you wrote does make sense, and I had noticed that it behaves the opposite of the CAB implementation on AMOLED screens (where it dims on lighter colored content)...so that gives even more credence to what you're saying, but the implementation is a little buggy. It transitions abruptly and causes the "flickering" that many have reported. I certainly wouldn't mind having it enabled if the transitions were slower/less frequent, but it's kind of annoying as it is. I never was able to find a way to disable it in the stock kernel anyway, so hopefully it can be fixed one way or another now that the source is available. Still the best phone I've owned!
So any success with any method here or elsewhere?
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
antinorm said:
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
Click to expand...
Click to collapse
i'm thinking it's CABL, but it's kernel level, NOT software level, which is why disabling it does absolutely nothing.
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Rayan said:
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Click to expand...
Click to collapse
it's not an issue with auto brightness, that's a completely different problem.
this is the content adaptive backlight problem.
so no solution was ever found for this (besides a new kernel)? my phone doesn't flicker but on the brightness below 50% i can notice it's trying to readjust itself slightly once in awhile (with xda app or play store for example).
Encountered this issue as well. So, the cause of this has something to do with the software and not the hardware? Don't want to send my phone back just to receive yet another problematic set.. I set my screen brightness to 38 which it flickers on certain photos and apps. Bumped it up to about 45 and it seems to have stopped.
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...)