S-View Cover Flow for Automate - Galaxy S 5 Themes and Apps

This is a flow I created with the help of Ben Rapaport in the CM Forums. It is a small program that uses the S5's proximity sensor to adjust the screen to the S-View Cover's window.
Directions before running this flow:
Make sure to navigate to Settings > Language & input, and turn the "High touch sensitivity" option on.
If you do not have the Automate app, install it. You can get it from Google Play. Make sure it is version 1.1.8 or later!
Open Automate. Tap the three dots in the top-right, then tap "Import". Find the flow that you downloaded from this thread and tap it to import.
The flow should be named "Samsung Galaxy S5 S-View Screen Resize". Tap the flow in the main menu and tap "Start" to run it!
Some things to note:
If you are running Android Lollipop/CyanogenMod 12 or earlier, you may notice that the screen does not resize well, if at all. This flow works best on Android Marshmallow/CyanogenMod 13 or later. We're still not sure why; perhaps the flow is too new?
The flow automatically enables the power save setting in your device's ROM when activated. You may deactivate this, but then it will heavily drain your battery! To do this, delete both blocks that enable and disable power save, then trace a line from YES on the proximity sensor block to IN on the shell command block containing "wm overscan #, #, #, #", and another line from No on proximity to IN on block with "wm overscan reset". If more people have issues with power save, I'll gladly add an alternate package to this post!
The screen may adjust improperly, depending on the size and position of your S-View window. Fix this by editing the numbers in the superuser shell command "wm overscan". Default values are 40, 0, 60, 950.
Trebuchet has issues with the flow, and may not appear when the cover is closed.
If you have any problems with this flow, feel free to discuss your problems below, and I'll try to help!
If the zip does not contain a file named "SamsungGalaxyS5S-ViewScreenResize.flo", please let me know! This is a free, password-less zip for anyone to share, use and modify. I do not accept donations - like I said, it's free! :angel:

CyanogenLover said:
This is a flow I created with the help of Ben Rapaport in the CM Forums. It is a small program that uses the S5's proximity sensor to adjust the screen to the S-View Cover's window.
Click to expand...
Click to collapse
thanks
1- please release some screenshot
2- you mean in cm13 rom that not supports s-view flip cover, by this program, s-view works in cm roms?

mohammad105 said:
you mean in cm13 rom that not supports s-view flip cover, by this program, s-view works in cm roms?
Click to expand...
Click to collapse
I guess you're asking if the flow works on CM? The answer is yes. I just haven't gotten it to work with CM 12 and earlier.

CyanogenLover said:
I guess you're asking if the flow works on CM? The answer is yes. I just haven't gotten it to work with CM 12 and earlier.
Click to expand...
Click to collapse
i was installed the cm12 and cm13 roms. both of them are very good rom. but none of them supports s-view flip cover. that means when i close flip cover, no display was shown.
so my question is: is your apk for s-view? what s-view?in cm13, s-view not exists
just that is my problem. the cm roms are very very good but not have samsung apks

mohammad105 said:
i was installed the cm12 and cm13 roms. both of them are very good rom. but none of them supports s-view flip cover. that means when i close flip cover, no display was shown.
so my question is: is your apk for s-view? what s-view?in cm13, s-view not exists
just that is my problem. the cm roms are very very good but not have samsung apks
Click to expand...
Click to collapse
It is not an APK. It's a flow that goes with the Automate app. Please read the first post more thoroughly!
It should work with CM 13. If you have further problems, please post them!

CyanogenLover said:
It is not an APK. It's a flow that goes with the Automate app. Please read the first post more thoroughly!
It should work with CM 13. If you have further problems, please post them!
Click to expand...
Click to collapse
i was follow the 1st post and install the apk and import your attached file and set all permissions for apk. but the following error occurs:
fail [email protected]: java.lang.illegalstateexception: failed to set power save mode (not allowed)
and the error: not running occurs. so the flo file not runs up to now

mohammad105 said:
fail [email protected]: java.lang.illegalstateexception: failed to set power save mode (not allowed) and the error: not running occurs.
Click to expand...
Click to collapse
Are you giving it superuser permissions? You must have this to be able to run the flow.
If that doesn't work, try disabling the Power Save part of the flow. You can delete it from the flow, but don't forget to draw the connections back!

CyanogenLover said:
Are you giving it superuser permissions? You must have this to be able to run the flow.
If that doesn't work, try disabling the Power Save part of the flow. You can delete it from the flow, but don't forget to draw the connections back!
Click to expand...
Click to collapse
yes i give superuser permission for that
i think that the power saving apk not exists in cm13 rom !!!!
and i delete the power saving block, but this error occur continusly
and how can link blocks after deleting the power saving blocks?
may you create a new one and attach it? thanks
and a question: if this file works correctly, after closing s-view flip cover, the phone turns off or the screen of s-view has been shown?

mohammad105 said:
i think that the power saving apk not exists in cm13 rom !!!!
and i delete the power saving block, but this error occur continusly
and how can link blocks after deleting the power saving blocks?
may you create a new one and attach it? thanks
and a question: if this file works correctly, after closing s-view flip cover, the phone turns off or the screen of s-view has been shown?
Click to expand...
Click to collapse
The Power Save feature uses a setting into the CM ROM. It's possible that Power Save is not present in your version. You could flash a different ROM and try my flow again.
If you'd rather try to remove the Power Save feature, did you remove both blocks related to Power Save? One block turns it on when the cover is closed, the other turns it off. To get rid of the Power Save altogether, remove the Power Save enable and battery blocks, then trace a line from YES on proximity to IN on the shell command "wm overscan #, #, #, #". On the other side, remove the Power Save disable block, and make a line from NO on proximity to IN on "wm overscan reset".
I also have had the issue you are describing with closing the cover. I assumed that the problem was fixed in CM 13 when I upgraded, but I could be wrong. Perhaps Ben could look into that problem.
UPDATE: Added these instructions to the first post. Please let me know if any of you users have further problems with power save, and I'll upload another ZIP containing an alternate flow that has it removed.

CyanogenLover said:
The Power Save feature uses a setting into the CM ROM. It's possible that Power Save is not present in your version. You could flash a different ROM and try my flow again.
If you'd rather try to remove the Power Save feature, did you remove both blocks related to Power Save? One block turns it on when the cover is closed, the other turns it off. To get rid of the Power Save altogether, remove the Power Save enable and battery blocks, then trace a line from YES on proximity to IN on the shell command "wm overscan #, #, #, #". On the other side, remove the Power Save disable block, and make a line from NO on proximity to IN on "wm overscan reset".
I also have had the issue you are describing with closing the cover. I assumed that the problem was fixed in CM 13 when I upgraded, but I could be wrong. Perhaps Ben could look into that problem.
UPDATE: Added these instructions to the first post. Please let me know if any of you users have further problems with power save, and I'll upload another ZIP containing an alternate flow that has it removed.
Click to expand...
Click to collapse
thanks. i can't draw a line between blocks
how you did this?

mohammad105 said:
thanks. i can't draw a line between blocks how you did this?
Click to expand...
Click to collapse
Drag your stylus/finger from one point to another. It's a little sensitive, so you may have to try multiple times. Move the blocks around, if you need to.

CyanogenLover said:
Drag your stylus/finger from one point to another. It's a little sensitive, so you may have to try multiple times. Move the blocks around, if you need to.
Click to expand...
Click to collapse
finally works
very good . thank you
the windows size is very good for flip cover
i have some suggestions:
1- we can edit this flowchart to lock the phone immediately when we close the cover and unlock the phone after opening s-view cover
2- the speed of reaction is a little low
3- as i know, the sensor of s-view flip cover is not proximity sensor. it uses magnet proximity. could you find the sensor of flip-cover and replace that with proximity sensor for this flowchart?
thanks
---------- Post added at 11:29 AM ---------- Previous post was at 11:19 AM ----------
Here is an apk file that diables the s-view function from developer, MohammadAG
http://forum.xda-developers.com/showthread.php?t=2391549&page=2
by this apk file, we can find the associated files for s-view

mohammad105 said:
3- as i know, the sensor of s-view flip cover is not proximity sensor. it uses magnet proximity. could you find the sensor of flip-cover and replace that with proximity sensor for this flowchart?
Click to expand...
Click to collapse
Actually, this may vary with each cover. The S-View cover I have seems to not be magnetic at all; it is a very simple cover made by Samsung for the Galaxy S5. I can add a flow with a magnetic sensor instead of proximity, but as there was no noticeable change in the magnetic field upon testing by closing and opening my cover, you may have to set your own values!

CyanogenLover said:
Actually, this may vary with each cover. The S-View cover I have seems to not be magnetic at all; it is a very simple cover made by Samsung for the Galaxy S5. I can add a flow with a magnetic sensor instead of proximity, but as there was no noticeable change in the magnetic field upon testing by closing and opening my cover, you may have to set your own values!
Click to expand...
Click to collapse
if the cover is works with proximity sensor, why when we put our finger on the proximity sensor in top of the phone, the screen not off???
the magnetic sensor is not true, because i tested it now, and the magnetic field not changes. idon't know what sensor uses for proximity sensor
and another thing that: your flo file is proximity sensor based that when suddenly our finger go on the proximity sensor, suddenly the screen of phone changes i think and change the proximity with light sensor (value 0-9) why light sensor? because is low sensivity and good
and add two block to chart way: 1- lock phone and 2- brightness=50%
why? because i want to when i close the flip cover, phone locks automatically and the brightness of phone go to 50% because of dim screen when s-view closed
is that good?
but the problem is when that i go to a dark room and suddenly the screen closes and go little , because of using light sensor

mohammad105 said:
the magnetic sensor is not true, because i tested it now, and the magnetic field not changes. idon't know what sensor uses for proximity sensor
Click to expand...
Click to collapse
Well, if you'll notice when installing the cover, there are two connectors on the inside that fit in designated slots. You can see them in this picture (the gold prongs by the camera hole).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That may be a clue to how the cover is supposed to work. ​

CyanogenLover said:
Well, if you'll notice when installing the cover, there are two connectors on the inside that fit in designated slots. You can see them in this picture (the gold prongs by the camera hole).
That may be a clue to how the cover is supposed to work. ​
Click to expand...
Click to collapse
yes . the notice is there that how works this cover?

mohammad105 said:
yes . the notice is there that how works this cover?
Click to expand...
Click to collapse
I'm not sure what you're trying to say. I think you meant "I see what you mean. How does the cover work?"
Perhaps this needs Google-ing, Yahoo!-ing, DuckDuckGo-ing, or whatever. Or, maybe a cover needs to be taken apart to see how it works.
@Benrap, care to inout your ideas?

CyanogenLover said:
I'm not sure what you're trying to say. I think you meant "I see what you mean. How does the cover work?"
Perhaps this needs Google-ing, Yahoo!-ing, DuckDuckGo-ing, or whatever.[emoji14]Or, maybe a cover needs to be taken apart to see how it works.
@Benrap, care to inout your ideas?
Click to expand...
Click to collapse
In stock, pretty sure the cover works using both magnetic and proximity sensors. When it senses both a strong magnetic field and sees there is something close by, it enters the mode with the little window. All this happens if the phone has been connected to an s-view cover with the little chip at the back, which tells the phone what colour the cover is, and the fact that it is manufactured by Samsung.
With @CyanogenLover 's flow it works with only the proximity sensor (something i disagree with - should be with both proximity and magnetic sensors), and without the chip testing at the back (pretty much impossible without being an amazing incredible awesome flabberghasting genius nerd)

Benrap said:
In stock, pretty sure the cover works using both magnetic and proximity sensors. When it senses both a strong magnetic field and sees there is something close by, it enters the mode with the little window. All this happens if the phone has been connected to an s-view cover with the little chip at the back, which tells the phone what colour the cover is, and the fact that it is manufactured by Samsung.
With @CyanogenLover 's flow it works with only the proximity sensor (something i disagree with - should be with both proximity and magnetic sensors), and without the chip testing at the back (pretty much impossible without being an amazing incredible awesome flabberghasting genius nerd)
Click to expand...
Click to collapse
I have create a flowchart that check both of "ambient light" and "proximity sensor" to lock automatically and resize the windows size when s-view cover close
here is my flowchart screenshot:
but when i close the s-view cover, the magnetic sensor not sense the magnetic subject of s-view, but when i close the phone to a magnetic field, the sensor works fine that's why i create both of light and proximity sensor that when suddenly your finger puts on proximity sensor, the phone dont go to resize and lock

mohammad105 said:
I have create a flowchart that check both of "ambient light" and "proximity sensor" to lock automatically and resize the windows size when s-view cover close
here is my flowchart screenshot:
but when i close the s-view cover, the magnetic sensor not sense the magnetic subject of s-view, but when i close the phone to a magnetic field, the sensor works fine that's why i create both of light and proximity sensor that when suddenly your finger puts on proximity sensor, the phone dont go to resize and lock
Click to expand...
Click to collapse
Nice idea.

Related

[Q] Is there a fix for a broken proximity sensor in CM 10.1?

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

[Q] Galaxy S4 Proximity Sensor disable

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...)

[MOD][XPOSED] Force Touch Detector

**** THIS PROJECT IS NO LONGER MAINTAINED ****
Force Touch Detector
Force Touch Detector (FTD) is a Xposed module to detect Force Touch and switch touch action. FTD assigns seven force actions:
Tap
Double Tap
Long Press
Flick Left
Flick Right
Flick Up
Flick Down
Of course FTD doesn't bother normal operation by the threshold of pressure.
Introduction
Android reports pressure of your touch when you tap, press, swipe, and so on. However the pressure is different from Apple's Force Touch Technology. (It is mechanical implementation, isn't it?) Android's pressure is depending on touch area of your finger, not strength. But the touch area provides us new UI.
Force Touch on Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you touch with the ball of your finger, the touch area increases. Call this "Force Touch" in this project. It is possible to distinguish ordinary touch operation from deliberately Force Touch because there is a distinct difference between these touch area. By checking whether a touch event is started from Force Touch, you can change the action of the touch.
Example:
Open floating launcher when you do force tap that is a tap started from Force Touch.
Go back by performing force flick to right that is a flick started from Force Touch.
Expand notifications by performing force flick to bottom anywhere.
Getting Started
At first, check your hardware supports FTD functions or not. Open a threshold screen, Pressure -> Threshold, and then test tap and force touch with two buttons. If Max, Pressure and Ave are changed by each touch, your touch screen supports the pressure parameter, you can use FTD by pressure. If not so, your phone doesn't support pressure, next try Size -> Threshold screen.
Note that some smartphones don't support both the pressure and the size parameter. FTD doesn't work on such a device.
After checking the capability of your touch screen, practice and adjust Force Touch with Threshold screen. Tap small button and do force touch on large button 5 times or more respectively, you'll get a Max value for normal tap and an Ave value for force touch. The Ave value must be higher than the Max value, you should practice force touch until so.
Finally, input a number between the Ave and the Max, and turn Master Switch on.
Adjustment
There are 3 parameters to adjust sensitivity for force touch.
Threshold
When pressure or size of your touch exceed this value, it is recognized as a force touch.​Detection Window
The length of time FTD waits for force touch. If zero, FTD checks only the beginning of your touch stroke.​Detection Sensitivity
The sensitivity for force tap and flick. If zero, Force Touch is always interpreted as a flick. If too high value, it is always tap. The range is 0 to about 20, depends on hardware.​
I propose two strategies for adjustment.
Long detection window and high threshold value
Short detection window and mid threshold value
Maybe the experience of the former is near to Apple's Force Touch, squashing. However Android devices detect the pressure of touch by touch area even if you enable Pressure Threshold. In the other words, FTD's Force Touch based on Android API and Apple's one are fundamentally different. So I recommend to try both strategies.
Pressure vs. Size
These touch parameter depend on your hardware. Some phones report both parameters, some phones report only one parameter, and there may be some phones that don't report neither.
Reported Devices (shared/editable spreadsheet)
Compatibility
I tested on Nexus 4 running AOSP 5.1.1.
Q&A
Q. Does this mod work on my phone?
Activate the pointer location in dev options to see your touch pressure and size. If they are always same value, your hardware doesn't support them.
Download
Xposed Module Repository
XDA:DevDB Information
Force Touch Detector, Xposed for all devices (see above for details)
Contributors
tkgktyk
Source Code: https://github.com/tkgktyk/ForceTouch
Xposed Package Name: jp.tkgktyk.xposed.forcetouchdetector
Version Information
Status: Stable
Stable Release Date: 2015-07-28
Created 2015-06-08
Last Updated 2016-10-25
can you make how to video?? cant seem to get it work.
I dont really get what is the advantages of this module.. ?
Interesting.
Love to see a video too.
Very interesting concept! Love to see more information about how to "properly" use this module.
By the way dev, isn't there already a thread for this module earlier? Have you upgrade the module so a new thread is open as well?
Great job! Will give it a try now~
Vídeo for us
Works with CM12.1 ?
HGT - S5 G900F - Oneplus One - Tesla TTL7
I found out how it works on my z3 running Android 5.0.2.
What the developer means with his explanations is that you don't use the tip of your thumb but instead you place the thumb flat on the screen. You press or long press or swipe as usual, except you do it with the thumb flat on the screen. Don't press harder or in any different way then usual except of the thumb being flat.
Open the app, forget about half the settings and all the explanations and simply put "pressure threshold" to 0.7 and assign desired actions to the different commands. For example: click on the action "tap", chose "apps" and chose "YouTube". Then go to your homescreen (or into any other app) to test. You can not test while the module itself is in the foreground.
If you do it right, the "press with flat thumb" doesn't count as a normal press. This means you can press anywhere to execute the command, without ab care for what would happened if you pressed normally at same spot.
It takes some practice but once you got it, you got it. A good module with potential.
set to 0.8 on the OnePlus One (CM 12.1)
https://youtu.be/Xj0AMN5lHD0
Moto g LTE with 5.1
Works fine, set up to 0.6
I think that would be great to limit the area where we input a force touch, maybe in the bottom area of the screen.
Everyone, I apologize for any confusion.
#8 posted by @android404 and #10 posted by @k0sTi are great helpful. Thanks a lot!
@android404;
Many thanks! "press with flat thumb", yes, that's all!
I wanted to explain as you said. I'm going to simplify Pressure Threshold screen.
sclcn12 said:
Moto g LTE with 5.1
Works fine, set up to 0.6
I think that would be great to limit the area where we input a force touch, maybe in the bottom area of the screen.
Click to expand...
Click to collapse
The implementation is easy probably. I try to append your suggestion.
Thanks!
Looks like it's not working for me. Used 0.75 and rebooted, all touches are reported as "force touch" in a toast. Tried 0.95 same ****. I had to delete apk using twrp as normal touch wasn't working.
Blisspop 5.1.1
( back now, but still no reply ?)
andreasf93 said:
Is there a chance you can do mine as well?
Click to expand...
Click to collapse
Oh, I was overlooking your post. It's my fault, sorry.
I'm sure simulating taps is OK, but I need time for long press. Simulating one tap is unnecessary, isn't it? I'll focus dtap and long press.
Need help, this module is not working for me. wherever i click on the screen a toast appears telling the force touch pressure. I can unlock the phone but that is as far as it goes, unable to access xposed module or any other app. How do i uninstall or access this module, please help.
I get touch pressure of 1 no matter what i do . Any value below one , all touches are considered forced. However it works perfectly with my s pen.
andreasf93 said:
Great module, seems to be working fine so far (Nexus 5, set at 0.7500). I have a request tho, can you make an action (tap/dtap/long press) simulate another action? For example, I would like a tap to simulate a long press.
EDIT: Btw this is very similar to Mohammad's one (http://repo.xposed.info/module/com.mohammadag.systemwideforcetouch) but his module doesn't work on 5.1 while this one does.
Click to expand...
Click to collapse
I would be a great improvement if it could implement these actions. I would like it to simulate long press.
Hi, tkgktyk.
Constant force close. Here is the xposed log, I hope it helps. http://pastebin.com/0tz04TcN
P. S. : Can't a arch log, please, use pastebin to get it.
Sent from my Galaxy Note III LTE
v0.1.3
I uploaded wrong apk as v0.1.2.
Please skip v0.1.2 and update to v0.1.3.
** WARNING **
(SOFT)REBOOT IMMEDIATELY AFTER UPDATING
+ Master Switch
+ Notification to disable while running
+ Limit detection area on screen
+ Force touch effect
> Remade "Pressure Threshold" screen
> Added double tap and long press action
>>> but only interface
mobihack said:
Looks like it's not working for me. Used 0.75 and rebooted, all touches are reported as "force touch" in a toast. Tried 0.95 same ****. I had to delete apk using twrp as normal touch wasn't working.
Blisspop 5.1.1
( back now, but still no reply ?)
Click to expand...
Click to collapse
I remade "Pressure Threshold" screen to practice Force Touch. Please try this.
satanoncrack said:
Need help, this module is not working for me. wherever i click on the screen a toast appears telling the force touch pressure. I can unlock the phone but that is as far as it goes, unable to access xposed module or any other app. How do i uninstall or access this module, please help.
Click to expand...
Click to collapse
The solution is the same as during bootloop. Flash Xposed-Disabler-Recovery.zip to disable Xposed framework at recovery. or refer to http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816 for lollipop.
Added notification to disable this mod in v0.1.3!
j-a-c-k said:
Hi, tkgktyk.
Constant force close. Here is the xposed log, I hope it helps. http://pastebin.com/0tz04TcN
P. S. : Can't a arch log, please, use pastebin to get it.
Sent from my Galaxy Note III LTE
Click to expand...
Click to collapse
I'm sorry to trouble you, I uploaded wrong apk as v0.1.2. I forgot to rebuild apk at last after modifying.
I uploaded next apk v0.1.3 rebuilt surely.
After updating, please clear data of FTD before launching it.
Ok managed to download the latest version by accessing the website since going to xposed app shows only the old version. Gonna try the new one and report back.
Ok latest version installed , soft rebooted as instructed , dalvik cache got wiped after soft reboot, however the same issue is there , no matter how I touch The screen the pressure is always 1. Any value below 1 all touches are considered forces touches. Note edge running Resurrection remix 5.4.7.

Gravity screen - use flip case and trouser-function in parallel

hi,
i use my redmi note 2 with a flip case but want to have the rouser function in use as well, that means:
- having the flip case closed and take it out of the trouser in front of my face: display turns on
- having the mobile on the table and open the case: display turns on
- having the mobile on the table and close the case: display turns off
- having the mobile on the table and case opened, take up phone and lay it back: display turns off
is that possible? i tried lots of combinations, but that is not working...
regards,
astrakid
There's an app called "Gravity Screen" on Google Play Store at the moment, which has everything you mentioned .You need to be rooted and maybe xposed has to be installed. If you are on an AOSP rom, then you can use it with ease. But I'm not sure with MIUI roms.
The flip case cover the proximity sensor?
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
The flip case cover the proximity sensor?
Click to expand...
Click to collapse
yes, and it works in general as well, but in combination it doesn't as I desire.
edit: i am running an aosp rom (android 5.0.2) with xposed and gravity. but gravity doesn't offer features like gravity screen, does it?

How do I turn the Proximity sensor off?

Through testing I have determined that the "phone-going-automatically-to-speakerphone", any time I pull my head more than five inches fro the screen during a call, is due to the proximity sensor. It was not like this before the latest update.
I defeated this by placing a tiny piece of black electrical tape over the proximity sensor.
I would rather just turn the proximity sensor off, or at least turn the "automatically going to speaker phone) function off, but in past requests no one seemed to know how to do that.
So, I am left with just turning off the proximity sensor off.
Anyone know how?
Thanks.
MB
Variant: LGH932 Unrooted, stock firmware
Update: November 1st 2018 security patch
papamalo said:
Through testing I have determined that the "phone-going-automatically-to-speakerphone", any time I pull my head more than five inches fro the screen during a call, is due to the proximity sensor. It was not like this before the latest update.
I defeated this by placing a tiny piece of black electrical tape over the proximity sensor.
I would rather just turn the proximity sensor off, or at least turn the "automatically going to speaker phone) function off, but in past requests no one seemed to know how to do that.
So, I am left with just turning off the proximity sensor off.
Anyone know how?
Thanks.
MB
Variant: LGH932 Unrooted, stock firmware
Update: November 1st 2018 security patch
Click to expand...
Click to collapse
Why did you open a new thread when you had already started this one on the same topic?
https://forum.xda-developers.com/lg-v30/help/v30-automatically-goes-speakerphone-t3886240
My US998 20G (January 2019 security update) does not have that proximity sensor/automatic speakerphone feature.
I would love that feature, because if I need to check something on my phone during a call, I can keep listening/talking to the person on the call. It's actually a feature you can enable on many custom ROMs, like Resurrection Remix.
I'm curious why you do not like it?
papamalo said:
I would rather just turn the proximity sensor off, or at least turn the "automatically going to speaker phone) function off, but in past requests no one seemed to know how to do that.
So, I am left with just turning off the proximity sensor off.
Click to expand...
Click to collapse
You can try this:
Settings/General/Acessability/Vision/Talkback/Settings/Use Proimity Sensor - turn off.
There's also various apps that claim to turn off/disable proximity sensor.
You may be able to enter the H932 hidden menu and turn off the proximity sensor.
https://forum.xda-developers.com/lg-v30/how-to/tmo-v30-hidden-menu-t3753465
"Talkback is not installed"
Should I install it to disable something else?
And WHAT secret hidden ninja invisible menu?
Thanks!
papamalo said:
"Talkback is not installed"
Should I install it to disable something else?
And WHAT secret hidden ninja invisible menu?
Thanks!
Click to expand...
Click to collapse
See post #1 of the link I included.
The hidden menu has calibration, and other technical features not available to normal people, thus it's called the "hidden menu". Be very careful messing with anything in there, however. One time I screwed up something in there and had to do a Master Reset (got stuck on one LTE band).
---------- Post added at 08:09 AM ---------- Previous post was at 07:12 AM ----------
papamalo said:
"Talkback is not installed"
Should I install it to disable something else?
Click to expand...
Click to collapse
That came up when doing Google search for disabling proximity sensor. Some handicapped people need to bring the phone very close to their face without the screen going dark, so that was the suggestion for them on how to turn off proximity sensor. I thought it might work for you also.
What you want to do is very unusual -- turn off proximity sensor to disable a feature only you seem to be complaining about. I'm just trying to give information.
Thank you Chazzmatt! I wasn't trying to seem like I didn't appreciate the help.
For me it doesn't work because I work with my phone and it going automatically into speakerphone ode reveals Private client information to others who may be standing nearby.
But thanks. I figured out how to make it work. I simply places a tiny (one eighth of an inch) piece of black electrical tape over the sensor, and now it's fine.
Thanks again.
Papamalo

Categories

Resources