**** 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.
Related
Bear with me here, this issue is kind of hard to describe. When I am playing a game that requires touch inputs from both hands, I often get bugs. It's most obvious in games that have controller-style overlays. As is normal, I am using my left thumb to tell a character to move right or left, and then I press the button on the right to jump. However, when I release my jump, I stop running. The screen no longer recognizes that my left thumb has been pressed down the whole time and should still be moving in the direction I am pressing. This happens in Bean's Quest, Chono'n'Cash, Delver, Gunman Clive, and any other game of this nature I have tried on my device.
I played some of these games just fine on my old Evo. Is anyone experiencing this issue? I experienced it on stock as well as several custom roms I have tried.
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
gutrrob said:
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
Click to expand...
Click to collapse
Doesn't seem to have fixed my issue, I am still having problems with some two finger games. I will be using two fingers just fine, when I remove one finger from the display the first finger is no longer recognized even though it is still touching. I have to remove the first finger and press it again every time.
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
ryanalan82 said:
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
Click to expand...
Click to collapse
Appears that widgetlocker is the culprit! Is this issue documented or known, exactly? What causes it? Thanks so much for the help. I will surely miss widgetlocker.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I encountered this recently
It seemed to get "stuck" after using multi touch gestures in-game. Tapping the game with two fingers often "unstuck" it, but overall it was extremely frustrating.
This was on an APK not designed for the phone, though
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Racer Of All said:
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Click to expand...
Click to collapse
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
ryanalan82 said:
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
Click to expand...
Click to collapse
Did you try my edit 2? The Retain System keyguard? I can assure you that I have Widgetlocker installed and I have the 10 inputs (that video was recorded with widgetlocker running).
[SOLVED!] - HTC Evo 4G LTE touch screen trouble - WidgetLocker is the problem
Retaining system keyguard in WidgetLocker worked for me! Thank you for this Racer for All. (Actually I found your YouTube video, and a link to this thread)
I was wondering why all the games I played all of a sudden stopped functioning properly (in terms of touch controls... Example: MineCraft PE, moving forward and trying to look left or right - suddenly character would stop moving.)
Sorry to dig up an old thread, but I want people to know if they have WidgetLocker (and don't want to uninstall it) just go to Settings - Advanced - Retain system keyguard - zmag
Change the minimum brightness level from usual 10 to 1. It doesn't modify the autobrightness level map so automatic brightness won't be lowered (though it can be easily adjusted on CM11).
This is so far exactly the same as GravityBox offers (modifying 'config_screenBrightnessSettingMinimum').
But Minimum Brightness offers one unique feature - it also modifies the lower brightness levels in MX Player (free/paid). Because no matter whatever you use manual or auto brightness, MX Player always uses minimum brightness of 0.05 (12/255, 19/255, 27/255, 36/255...). To actually lower the brightness, you would have to turn off brightness control in MX Player or use one of many 'overlay filter brightness app'.
So Minimum Brightness module retains the same quadratic function for brightness levels but includes lower values (1/255, 4/255, 9/255, 16/255, 25/255...).
Minimum Brightness uses value 1/255 which might not be suitable for every display (meaning LCD) but it suits perfectly my Super AMOLED screens (Galaxy S5 / Galaxy Tab S 8.4) and watching videos at night is still enjoyable.
There are many excellent auto brightness apps (Lux, Darker etc) that can use overlay filters to lower brightness even more so it's up to everyone to try and decide.
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hello! Thanks for the mod, I will test
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
_mysiak_ said:
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
Click to expand...
Click to collapse
The situation is the same on my Xperia SP. When I set the brightness to miniumum the screen is totally black, also when the backlight decreases after 10 seconds screen gets black.
Hi! Tried min brightness but when screen is set to the lowest level, I get a white screen after locking the phone.
Sent from my DIAMOND D1 using XDA Free mobile app
Really great tweak!! I'm noobie in Android enviroment with my new Elephone P3000S and the lowest screen brightness is to high for me so your tweak is very usefull.
I also have the issue that the lowest brightness level sets the screen completly black and I have been scared for 1 hour truing to solve a completely black, touching all buttons but the phone didn't "wake up". Finally, pressing power buttom + volumen up + home soft key it has worked :angel:
So it would be very important to prevent black screen by allowing the user to set the minimun level.
Thanks!
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Dri0m said:
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Click to expand...
Click to collapse
I will have a new device soon so that could make me change my mind about lowest value and UI.
@Dri0m
In the first post you can find archive containing multiple versions of module with different low values.
How to disable this module...?
I installed this module last night, enabled it in Xposed Framework, but did nothing with it. Then this afternoon I opened the Settings menu, went to Display, and before I could do anything else I received a phone call. As I terminated the call, the screen flashed, the phone rebooted--and after restarting it is completely, or almost completely blank. If I repeatedly tap the power button I get a fraction-of-a-second glimpse of the SIM PIN screen at normal brightness. This leads me to the suspicion that, by some weird combination of bad luck and an accidental touch of a finger after terminating the phone call, that the Minimum Brightness somehow got set--although why the phone then rebooted I don't know.
Anyway, by luck and good judgement I finally managed to enter the correct SIM PIN and then the phone unlock PIN. However, I can do nothing else. The screen is still blank, and as the phone is currently unlocked I don't want to touch the power button. Before sending the phone back to the manufacturer or anything drastic like that, I would like to try disabling the Xposed Framework. Whilst trying to find something useful in Windows Explorer I found Xposed-Disabler-Recovery.zip in the Internal storage\Android\data\de.robv.android.xposed.installer\files folder on my phone. I assume that this should be what I need. However, as I cannot see anything on the screen I would need to know the exact buttons to press, in which order and how many times etc, in order to enter the Recovery menu and do what is needed. According to the phone manufacturer the OS is unmodified Android 4.4.2., although strangely they will not even tell me which keys to press to enter the Recovery menu (long story, the upshot is, they flat out refuse to help apart from suggesting returning the phone).
Note that I only suspect it is the Minimum Brightness module that is causing the problem, however the problem did not exist before yesterday (when I installed the module), and as I was about to do something with the brightness when the phone rebooted itself, it seems too much of a coincidence to be anything else. If I cannot disable the module/framework, the only other thing I can think of is a factory reset--but again I would need to know exactly which buttons to press, in which order etc. Unfortunately at the moment USB debugging is not enabled, and again without the screen I cannot access it to turn it on.
Any help or suggestions hugely appreciated.
PL
@Papalazzzaru
Xposed now sports a safemode which allows you to disable Xposed during bootloops. To disable Xposed, you'll have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup.
During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to easily troubleshoot problematic modules.
Sorted
Outstanding, thanks.
Papalazzzaru said:
I installed thi............. gely appreciated.
PL
Click to expand...
Click to collapse
Device model please?
Caterpillar S50, on Android 4.4.2, baseband version LTE_S0201121.0_S50_0.017.00.
it is compatible with lollipop?
imam88 said:
it is compatible with lollipop?
Click to expand...
Click to collapse
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Thanks, this is exactly what I want.
Could you make it for LP ?
I want my phone be absolute zero brightness for driving navigation.
Tested it on CM12.1 Nightly on the Nexus 6. It works here, but on 0 the screen is a bit purple. However, I guess this is the screen's fault
Gesendet von meinem Nexus 6 mit Tapatalk
moneytoo said:
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Click to expand...
Click to collapse
Yes it works
This module seems to be working well on the Moto X Pure Edition (Motorola xt1095) running Lollipop 5.1. It's an AMOLED screen, and I personally find the minimum brightness on 5.1 too bright, so this has helped solve that.
Hi all, can anyone who owns the tablet check if your set has this issue as well? I'm using the Mediapad M5 Pro.
Basically on my set there is a problem with the touchscreen whereby when making small adjustments, changing directions with small movement will cause the touchscreen to hang and cause the touch input to jump a few pixels.
Any help would be appreciated as I'm trying to figure if this is a hardware issue with my set or if its a software issue that affects all M5 Pro.
I have an inkling that this could be caused by palm rejection configuration of the tablet that is overly aggressive, causing the touchscreen to bug out as such.
Videos to illustrate problem: (use the direct links if the embedding doesn't work)
(in app drawer) https://youtu.be/Ni5xvRPgAdE
(in pubg mobile) https://youtu.be/mibyKmaXA0E
(in chrome remote desktop) https://youtu.be/vpmXleSaNZU
My M5 Pro is having this issue too...
Afaik there is a threshold level when to recognize an input as a "tap" and when as a "swipe/movement"
We humans are too inaccurate so that one tap often contains a movement by accident. To cancel that out minor movements are still considered taps.
Would be interesting to see if it is the same on lineage OS. If it is,then the reason is probably palm rejection or some weird thing. If it's not the reason is most likely how Huawei calibrated it.
At least that's what I think without any proof
lolmensch said:
Afaik there is a threshold level when to recognize an input as a "tap" and when as a "swipe/movement"
We humans are too inaccurate so that one tap often contains a movement by accident. To cancel that out minor movements are still considered taps.
Would be interesting to see if it is the same on lineage OS. If it is,then the reason is probably palm rejection or some weird thing. If it's not the reason is most likely how Huawei calibrated it.
At least that's what I think without any proof
Click to expand...
Click to collapse
Good point, but the thing is the jitters still occur after I start to scroll the pages. Afaik, upon the very first contact against the digitizer the system should identify if its a tap or scroll input. Once a scroll input is identified, the consideration for tap input should be nullified.
In that case if we were to refer to the videos I shown, as soon as my finger taps the screen and starts scrolling, the digitizer should be relaying information to the phone that it is a scroll, there is no reason for the phone to think that I am still performing a tap after I have been scrolling around without lifting my finger off the screen.
Of course, I am no coding expert and what I am stating here is based on logic and my limited understanding of computer language. So my point is I still think it's a software bug that Huawei needs to address and as evident on their past phones (P20 Pro, Honor 9), it is not the first time bad touch firmware has been heard of on a Huawei device.
**Another point is that if you were to perform the same test but instead with the M-pen, the touch screen would work just fine. But stylus touch input runs differently from finger touch input, so I am not too sure about how to comment on this.
jerronchua55 said:
Good point, but the thing is the jitters still occur after I start to scroll the pages. Afaik, upon the very first contact against the digitizer the system should identify if its a tap or scroll input. Once a scroll input is identified, the consideration for tap input should be nullified.
In that case if we were to refer to the videos I shown, as soon as my finger taps the screen and starts scrolling, the digitizer should be relaying information to the phone that it is a scroll, there is no reason for the phone to think that I am still performing a tap after I have been scrolling around without lifting my finger off the screen.
Of course, I am no coding expert and what I am stating here is based on logic and my limited understanding of computer language. So my point is I still think it's a software bug that Huawei needs to address and as evident on their past phones (P20 Pro, Honor 9), it is not the first time bad touch firmware has been heard of on a Huawei device.
**Another point is that if you were to perform the same test but instead with the M-pen, the touch screen would work just fine. But stylus touch input runs differently from finger touch input, so I am not too sure about how to comment on this.
Click to expand...
Click to collapse
I agree with you. They managed to fix the emui touch bug though where two simultaneous inputs were denied after a short time. (also was / is on the p10 and other emui devices)
And that's why I was curious about lineage OS.
The pen works with a different digitizer though. So different production, drivers etc
Not fixed even with the latest update with Gpu turbo...
anyone have solution for this??
i don't know if this is solution but there is 1 option. I don't know how is in english because i have polish language but if u
Polish - Ustawienia - inteligętna pomoc - Ułatwienia dostępu - Gesty powiększania
Translator google XD ???? - Settings - intelligent help - Accessibility - Gestures of magnification
when I have this option turned on, the touch screen responds very strangely and with an delays in all apps (games too)
DDragonDD said:
i don't know if this is solution but there is 1 option. I don't know how is in english because i have polish language but if u
Polish - Ustawienia - inteligętna pomoc - Ułatwienia dostępu - Gesty powiększania
Translator google XD ???? - Settings - intelligent help - Accessibility - Gestures of magnification
when I have this option turned on, the touch screen responds very strangely and with an delays in all apps (games too)
Click to expand...
Click to collapse
Is already off but still having same touch issue...
Anybody received this update?
Popped up today on my watch.
Didn't read the changelog, so i am trying to find it.
I updated and having issues with upper and lower buttons. When watch is awake pushing upper button takes me to last watch screen to the right, not as previously one by one. Pushing lower button doesn`t work at all. On 2.3.7. everything worked fine. I tried unpair and pair again, but the same problem is still present. Help someone?
Amazfit OS update log
Version: 2.3.8.0
Applicable equipment: Amazfit Stratos/Stratos +
- Update GPS firmware for more stable location service
- Update indoor running algorithm (recalibration of mileage)
- Added news notification support for Korean and Thai
- Added "3 data big words" - 3 data fields display mode for sports interface
- Added outdoor swimming automatic segmentation settings
- Added "Sports Reminder" - can be found at:
Settings on the watch > General > Sports Reminder
1. Sports start reminder: automatically recognize the running and walking mode after opening, will remind the corresponding sports mode after 5 minutes of activity, and save the official data before;
2. End of motion reminder: automatically recognizes the end state of running and walking after opening, reminds the end after 10 minutes of the end of the activity and automatically pauses the movement.
- Added music playback control function during sports (the watch will display the control screen on the last screen after the music is played)
- Optimize motion center rate accuracy
- Optimize connection stability for iOS devices
- Optimize emoji expression display (temporarily does not support non-standard emoji expressions, such as partial expressions of WeChat)
- Optimize the mileage display after the end of swimming
- Watch button functionality changes:
1. When using daily functions;
a. Short press on the upper button to return to the dial directly on any interface, press the list of applications on the dial interface;
b. Short middle button functionality unchanged;
c. Lower button press to change to the previous layer interface on any interface. If the current tab is at the widgets layer, return directly to the dial.
2. After unlocking in sports
a. Press upper button to alter motion;
b. Middle button short press is for selection;
c. Short press the button to change the motion control option. The option can be cycled.
- Widget layout adjustments
1. The right side of the dial becomes only up to two widgets, and the rest are placed in the watch application list (need to wait for the latest App push);
2. The “sports record” on the left side of the dial is moved into the watch application list.
- Optimized in motion interface
1. Increase the motion control interface in the interface during the movement, and slide to the right by sliding in the movement;
2. After pausing, support to switch to other motion data interface by sliding.
- Repairing abnormal work problems that may occur with watches in low temperature environments
- Fix the problem of swimming to calculate the number of steps
- Fixed some translation errors in English, French, and Italian
- Bug fixes
Don't update to this version. The new button functions seem to be really crappy.
I updated and hate it! Several good new options, but new buttons concept is awful!
SteffenBerlin said:
Don't update to this version. The new button functions seem to be really crappy.
Click to expand...
Click to collapse
I wouldn't say it's crappy, just something to get used to. If button layout were like that from the start you wouldn't even think about it. The change is just fine although I would like if they could be remapped or better yet remapped depending on the app.
But another issue in this version for me is that apk watchfaces do not work for me in sleep mode. It just shows blank screen. Anyone with this issue?
I just updated but it gives me problems with the watchface in standby of greatfit.
When unlocked the greatfit watchface is working but when locked the original or last selected watchface is showing.
Anyone got a fix?
Before the button layout was easy and effective. Upper and lower button for cycling thougth lists. Long press upper button for back. Now touchscreen has to be used. Buttons are almost useless. For Stratosfied I found a way to undo the new button layout. https://forum.xda-developers.com/sm...stratosfied-amazfit-amazfit-2-t3758506/page84 But it needs temporary root. How to get this? I already saw a lot of complains about the new button layout here and in Chinese forum. I should have read the update log completely before updating...
dude-nl said:
I just updated but it gives me problems with the watchface in standby of greatfit.
When unlocked the greatfit watchface is working but when locked the original or last selected watchface is showing.
Anyone got a fix?
Click to expand...
Click to collapse
Yeah, blank screen was showing to me in sleep mode when watch was restarted with non working apk watchface selected. But yes, some apk watchfaces (not all) also don't work for me in sleep mode anymore and is showing as you said last selected working watchface when in sleep mode or some other.
There is still Amazfit phone app that needs to be updated to reflect these firmware changes but nothing should change anyway.
TumiBC said:
Yeah, blank screen was showing to me in sleep mode when watch was restarted with non working apk watchface selected. But yes, some apk watchfaces (not all) also don't work for me in sleep mode anymore and is showing as you said last selected working watchface when in sleep mode or some other.
There is still Amazfit phone app that needs to be updated to reflect these firmware changes but nothing should change anyway.
Click to expand...
Click to collapse
On latest firmwares, US and CN, all watchfaces based on GreatFit don't work on standby mode and they need an update.
To disable the new key mapping, check this if you have unlocked bootloader: https://forum.xda-developers.com/smartwatch/amazfit/mod-amazfit-stratos-2-3-8-0-disable-key-t3890560
TumiBC said:
Yeah, blank screen was showing to me in sleep mode when watch was restarted with non working apk watchface selected. But yes, some apk watchfaces (not all) also don't work for me in sleep mode anymore and is showing as you said last selected working watchface when in sleep mode or some other.
There is still Amazfit phone app that needs to be updated to reflect these firmware changes but nothing should change anyway.
Click to expand...
Click to collapse
Yup. Same problem here. None of the APK watchfaces seems to be working now, and the buttons are pointless. 2.3.8. is the worse update ever. 2.3.7.0 was great, everything finally worked for me.
As far as I remember if you unlocked the watch and swiped up to the quick settings menu and tapped the weather it brought up the 5-day weather forecast. Is it just me or this also stopped working with the new firmware?
The new firmware is by far better in indoor (treadmill) exercise that before.
The estimated mileage is much more close to reality.
The pace calculation was practically useless in the previous version but now it is much, much better.
On the other hand, the changes they did to the buttons use, is awful for me...
Before I bought the watch, I have checked the official info in the app in Help/Amazfit Stratos where I could read what the buttons do (it is still there, btw). I made myself sure that I can fully control the device using only the buttons which is of fundamental importance to me (operating in rain/snow with gloves, etc).
I would NEVER buy a watch without such obvious (to me) functionality. Therefore, from my point of view the new firmware "update" made the watch unusable.
If that's important to you as well, do not update.
Same here. 3 buttons were a big selling point. Now they made them useless. Can't image why because it is not the native behavior of their UI. When pressing the upper button one can see scrolling over all widgets. However on all firmwares they have rolled out the new button layout users complain. But they stick on it.
I had tried to get into the new button arrangement. It is usable together with swiping indoor but total useless outdoor with gloves or at swim pool. That is totally lame.
Good. I still can return watches to seller.
With new firmware training load is not calculated any more. It is just 0. Anyone experienced same?
SteffenBerlin said:
With new firmware training load is not calculated any more. It is just 0. Anyone experienced same?
Click to expand...
Click to collapse
No, it works.
{
"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"
}
Sent from my OnePlus5
jacolagwa said:
Before I bought the watch, I have checked the official info in the app in Help/Amazfit Stratos where I could read what the buttons do (it is still there, btw). I made myself sure that I can fully control the device using only the buttons which is of fundamental importance to me (operating in rain/snow with gloves, etc).
I would NEVER buy a watch without such obvious (to me) functionality. Therefore, from my point of view the new firmware "update" made the watch unusable.
If that's important to you as well, do not update.
Click to expand...
Click to collapse
I agree, new buttons concept is useless outdoor by bad weather like snow and rain.
Developper should better work on fix thinks that does not work (like lap time) than destroying what works good.
@Wechy77: Thanks, yesterday it didn't calculate but today it did. I did not reboot nor factory reset. Hopefully it was only a temporary problem.
What is SideSqueeze?
SideSqueeze is an innovative and unique app that uses the barometric pressure sensor in your device to detect squeezes and screen presses. It is compatible only with Samsung Galaxy devices from 2017 onwards, although some people have reported varying degrees of success with Pixel devices.
What It Does
SideSqueeze gives your S8/S9/S10 series Galaxy the ability to respond to squeezes, double squeezes, triple squeezes, quadruple squeezes, long squeezes, and/or inertial squeezes, as well as force presses on the screen. For example, you can double squeeze your phone to activate Google Assistant...or maybe you'd like to quadruple squeeze to toggle auto-rotation. And now with Tasker integration, you can even create elaborate tasks to do just about anything and trigger them with any type of squeeze! SideSqueeze's new modular GUI allows you to pick and choose what you want to do with ease.
Features (not all available in trial version)
7 detectable squeeze types (single, double, triple, quadruple, long, long double-squeeze, and inertial)
3 detectable press types (single, long, and 2-finger)
Independently selectable criteria allow you to assign multiple actions to any trigger type (if lockscreen open, if homescreen open, if camera open, if S-Pen detached, if within 5-seconds of power on, if the phone is ringing, if in-call, or if screen is off)
New app picker to launch any app of your choosing
Tasker integration to launch any task of your choosing
Quick Settings tile to toggle detection engine
Wide selection of common actions, such as flashlight toggling, status bar toggling, etc
Adjustable pressure thresholds
Calibration assistant to customize SideSqueeze to your device's unique characteristics
Efficient detection algorithm that is designed to be as lightweight and low-power as possible with no significant impact on battery life
Questions?
See the in-app Help section for answers to commonly asked questions.
Where do I get it?
SideSqueeze 2 is now available on the Play store!
Screenshots
{
"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"
}
Yea, I tried Side Squeeze 1 when I first got the S10 a month ago and didn't work too well. I'll try the new version!
Ndaoud360 said:
Yea, I tried Side Squeeze 1 when I first got the S10 a month ago and didn't work too well. I'll try the new version!
Click to expand...
Click to collapse
Thanks! Also, keep in mind that if you're having problems you can use double-squeeze or triple-squeeze and keep single-squeeze disabled. Hopefully the new calibration stuff will help get it working better on your device.
Hi, this could be a useful app I think,but it didn't work on my s10e.I have calibrated and it read my pressure meters well,but there is no reaction when I squeeze it
Just tried this and it works great! I will be purchasing.
Hey man, super excited for this app. I have been a long time HTC user and the force sense was one of my favorite features. I don't think the app is quite ready for prime time yet though. I set my force pressure and calibration went well, but so far the device has only performed the way it should in 1 out of 10 tests. It also seems to set some kind of delay in between presses and squeezes. Hope you get these things ironed out, this would be really cool if you can get it working properly. Good luck.
rom116 said:
Hey man, super excited for this app. I have been a long time HTC user and the force sense was one of my favorite features. I don't think the app is quite ready for prime time yet though. I set my force pressure and calibration went well, but so far the device has only performed the way it should in 1 out of 10 tests. It also seems to set some kind of delay in between presses and squeezes. Hope you get these things ironed out, this would be really cool if you can get it working properly. Good luck.
Click to expand...
Click to collapse
Thanks for the feedback! If you still have it installed, can you go to the About tab, and tap "Send Report"? That will send me a list of all your SideSqueeze settings/values (nothing identifying). There is always a delay between things because it has to detect a pressure baseline again. Usually this takes 1-2 seconds.
ffolkes said:
Thanks for the feedback! If you still have it installed, can you go to the About tab, and tap "Send Report"? That will send me a list of all your SideSqueeze settings/values (nothing identifying). There is always a delay between things because it has to detect a pressure baseline again. Usually this takes 1-2 seconds.
Click to expand...
Click to collapse
Bummer, i uninstalled already. I probably waited at least 10 seconds.
ffolkes said:
Thanks for the feedback! If you still have it installed, can you go to the About tab, and tap "Send Report"? That will send me a list of all your SideSqueeze settings/values (nothing identifying). There is always a delay between things because it has to detect a pressure baseline again. Usually this takes 1-2 seconds.
Click to expand...
Click to collapse
Is there any way of removing the 2 second delay? Its really annoying and makes it hard to work.
Version 2.07 (just released to the store last night) offers better reliability and faster response-time, especially when "Disable baseline verification" is set (checked) on the settings panel (go to the About or Help tab, tap the gear icon on the top-right corner). Also, SideSqueeze is on sale for $1.99 through July 13th!
Hey, just got this and it works great! I'm thinking about donating
darthnater4ever said:
Hey, just got this and it works great! I'm thinking about donating
Click to expand...
Click to collapse
Thank you so much!
This is a fantastic app. So many possibilities. I've been testing both squeeze and screen press. I've tried multiple gain, multiple sensitivities, multiple calibrations, but it just never works out to be consistent.
I have them all setup to simply toggle the flashlight for now, andI just can't get them to toggle in a consistent manner. Even though I'm pressing as consistent as possible.
Actually as I'm typing this, I've noticed that while my S10 5G is on AOD, the squeeze sometimes inconsistently works, then stops. And when I press the power button to wake the phone up to the lock screen, the flashlight suddenly turns on or off, like the AOD was blocking the app from working all of a sudden. And then catches up to the last action it was supposed to do.
EG: On AOD, it was intermittently toggling on/off with squeeze, then stopped. So I pressed the power button to go to the lock screen. And as soon as I did this, the flashlight came back on itself, with the "turning flashlight on" message, wirthout me squeezing. Like the buffer of the app had caught up, as it was being blocked in AOD for some reason.
So it looks like something in the ap AOD is being blocked randomly/intermittently.
the_scotsman said:
This is a fantastic app. So many possibilities. I've been testing both squeeze and screen press. I've tried multiple gain, multiple sensitivities, multiple calibrations, but it just never works out to be consistent.
I have them all setup to simply toggle the flashlight for now, andI just can't get them to toggle in a consistent manner. Even though I'm pressing as consistent as possible.
Actually as I'm typing this, I've noticed that while my S10 5G is on AOD, the squeeze sometimes inconsistently works, then stops. And when I press the power button to wake the phone up to the lock screen, the flashlight suddenly turns on or off, like the AOD was blocking the app from working all of a sudden. And then catches up to the last action it was supposed to do.
EG: On AOD, it was intermittently toggling on/off with squeeze, then stopped. So I pressed the power button to go to the lock screen. And as soon as I did this, the flashlight came back on itself, with the "turning flashlight on" message, wirthout me squeezing. Like the buffer of the app had caught up, as it was being blocked in AOD for some reason.
So it looks like something in the ap AOD is being blocked randomly/intermittently.
Click to expand...
Click to collapse
Thank you, I will look into this.
Nice app. Great idea.
Would it be possible to add opening of edge panel via single squeeze?
I have a tough case that partially covers the screen edges making it difficult to swipe the panel out.
Great app and many thanks for it. I have one question: Is it possible to start voice or screen recording via squeeze in Samsung S10e?
I paid for tasker support in this app, and it cant even do that. Garbage **** app.
rom4ster said:
I paid for tasker support in this app, and it cant even do that. Garbage **** app.
Click to expand...
Click to collapse
SideSqueeze hasn't been updated in a long time, but an update is coming soon. It might fix the issue you are having with Tasker. I'd like to refund you, but you haven't reached out, so I don't know your order number or Play store email address.
ffolkes said:
SideSqueeze hasn't been updated in a long time, but an update is coming soon. It might fix the issue you are having with Tasker. I'd like to refund you, but you haven't reached out, so I don't know your order number or Play store email address.
Click to expand...
Click to collapse
I was going to but LUCKY for you and i guess me cuz its a whole process, There was a tasker update, and now app factory is not a steaming pile of **** and works flawlessly. What I did is i used app factory to turn my task into an app. Then used the "third party app" thing to launch the app version of my task. That works flawlessly so for the moment I am placated. LMK if the new update helps though. The whole reason i had to do this is because squeeze detection is not working great, but I understand reading sensor data for false squeezes is nigh impossible so that part im not that mad about, but if you got improvements ill happily take em.