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.
Related
As many of you have noticed, the notification light on the LGOG is annoyingly slow. In light of this, I sought out a solution. I've tried Light Flow, which worked well enough, but it wasn't quite what I wanted. I thought I was on to something with Tasker (awesome app!) and had something functional. Then I saw the great work from GermainZ here posted by TangoXray here and saw that it was possible to also include using the capacitive button backlights similar to BLN (back in the Samsung Captivate days). After a while of fiddling, I've come up with this Tasker-made app.
I designed it to be straight forward, yet have several options. It's a bit simpler to use than GermainZ's app, but is not as powerful or customize-able since it is designed specifically for the E970 (it may work with other devices, but I doubt it).
{
"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"
}
It requires:
1. Root Root is NO LONGER NEEDED!!!
2. Secure Settings (has a needed plug-in for Tasker and allows the screen to be woken up). The app will prompt for installation of this from the Play Store (it's FREE).
3. Accessibility enabled. The app has a button to quickly access it.
The options are:
1. LED on and off times (in milliseconds) are adjustable. However, it appears the system has a limit to how small of an off time is allowed.
Default: 1000 ms on and 100 ms off2. Notify duration (in seconds) for how long you want it to work before shutting off after a new notification. This way your lights aren't flashing for too long (this should be a battery saving measure if you suspect you might leave your beautiful phone alone for very long).
Default: 600 s (10 minutes if you needed help with the math )3. Screen On With Notify. When enabled, the screen will turn on momentarily (roughly 3 seconds) when a new notification arrives. I find this helpful so I can quickly look at the notification bar when the notification arrives without having to touch the phone.
Default: On4. Button Lights. When enabled, the button backlights will pulse at the rate specified with the LED on/off times.
Default: On5. LED Light. When enabled, the red notification light around the power button will pulse at the rate specified with the LED on/off times.
Default: On6. ONN Notification. When enabled, a notification will appear in the dropdown when you receive a new notification. This can be clicked to clear the light flashing, but still keep the message in the notification bar. This can also be set to permanent (until the notification is cleared). This is pretty much only useful if you "swipe" away your notifications. Since I haven't found a way to clear the light flashing from such an action, the lights will continue to flash until you open up one of the supported apps.
Default: On and On7. Clear On Unlock (Go Locker). When enabled, the ONN notification will clear and cancel the blinking when you unlock your phone. The app's notification that triggered the event will still be in your notifications. Now works with Go Locker (the only 3rd party lockscreen I've tried it with)! I assume that the stock lockscreen and Go Locker trigger in different ways. I hope to get it to work with other lockscreens.
Default: On (Go Locker Off)8. Clear On Screen On. When enabled the ONN notification will clear and cancel the blinking when the screen turns on. Even if you have the "Screen On With Notify" enabled, it will still keep the notification until you purposefully turn the screen on.
Default: On9. No Timeout While Charging. When enabled, the ONN notification and blinking will not timeout while your phone is charging. When you unplug, the timeout timer restarts.
Default: On10. Battery Level Cutoff %. When your battery is below this level, the ONN notification and blinking will cancel and no new notifications will trigger ONN.
Default: 20%11. Constant LEDs. When enabled, the lights do not blink, but rather stay on. This has the trade-off of not needing the app to use loops (helps with battery), but potentially uses more battery since the light is on more. More testing is needed to see if it hurts.
Default: Off12. No LED while Charging. Turns off the LED when charging so that the light is only used for notifications. The light will still turn on momentarily when you plug in the charger.
Default: On
There is also an option to test your settings. You just need to turn your screen off and then when you're done, click "stop". Be aware that the first time you use it, it may behave a little off until you grant root access. After this, it *should* work smoothly.
Right now, I have it set to trigger on notifications from:
Calendar
Email
Gmail
Google Voice
Messaging
Missed calls
Google Talk
Contacts +
K-9 Mail
WhatsApp
Line
To reset the notification, you can do one of the following:
Click on the notification
Click on the ONN notification in the dropdown (if enabled)
"Clear" the notification in the dropdown
Open one of the supported apps (you could open Gmail to clear a text, for instance)
Click the "Stop" button within the app (next to the "test" button)
Using #7 or #8 above
Other recommendations:
Inside the app SuperSU, you can set it to not show a "toast" notification each time. Otherwise, it gets a little annoying seeing "ONN has been granted superuser access" each time.
I have turned off the ONN Notification toggle so I don't get the extra icon in my notification bar (and so the new notification stays visible a little longer instead of the ONN Notification "scrolling" up.
Inside System Settings --> Display --> Notification Flash, turn off the "Use LED light for notifications". I'm not sure it would interfere, but I figure might as well leave it off so it doesn't cause issues.
When updating the app, if you encounter issues, clear the app data.
I will later try to add more features and spruce it up a bit. But for now, I think it's quite functional. Please let me know if there's anything not working or if something should be added. I'm new to app making with Tasker, so it's a bit of a learning experience. I have also attached the Tasker XML that I used to create the app in case anyone wants to use that or improve it.
Changelog:
v1.1
Fixed the Google Talk trigger
Added ability to clear notification by turning on the screen or unlocking the phone
Added no timeout while charging
Added auto-cancel when battery below user-specified value
Spruced up and modified the UI
Added "About" to the UI
v1.2
Fixed Messaging and Email clear (forgot to actually add these originally)
Added Go Locker unlock
Fixed lights getting stuck (prevented the task from disappearing when the screen is off)
Added support for Contacts + and K-9 Mail
v1.3
Added support for Line and WhatsApp
Added constant on for the LEDs toggle (instead of blinking)
-the red power LED will still pulse like it did for charging
Added "No LED while Charging" toggle so the LED is only used for notifications and not for charging.
-the light will still turn on momentarily and then turn off
Improved battery usage (hopefully).
-This *will* still use more battery than if you didn't use it since the lights are on longer than the stock notification interval
v1.3.1
Removed need for root (I no longer use the echo "255" script--instead, I saw that the max brightness for the button backlights is 3, so I could just use the Tasker function).
Two versions--one with the K9 Plugin (you will need to have K9 installed whether you want it or not), the other without the plugin so you don't have to install the app (it's free, so it's not a huge deal IMO). It will still work with notifications sent from the K9 app either way and opening the K9 app will clear notifications.
Made sure it works with Jellybean (thanks to gstar101 for catching the earlier incompatibility)
Bugs:
Still behaves a bit funny at first (specifically after the first install and before root access is granted)
*May* experience higher amounts of battery consumption. Please let me know if this happens (I've been getting roughly 3 or 4% battery usage from ONN).
TODO:
Find a way to get the screen on function to work without Secure Settings
Get 3rd party lockscreens (besides Go Locker) to cancel the notification
Add other apps to trigger ONN?
Eventually, I will release this on Google Play under my developer name "NanoTech". First, I'd like some feedback on what bugs need to be fixed or features that should be added. GENTLE feedback is appreciated!
Special thanks to GermainZ for answering questions about Tasker and putting up with me. Also, thanks to TangoXray for letting us know about ButtonLED in the LGOG forum.
Good job
You could probably make it work without secure settings: try using shell commands to control the screen's backlight. If I'm not mistaken, something like "echo 255 > path" will turn the screen on if it's off (you can then use the user defined variable for brightness, since Tasker can get that).
Good luck!
Edit: Actually, using an intent to turn the screen on should be much easier. I have the habit of over complicating things, lol. Google it if you like, not sure what the syntax is (you can either use the shell or the built in Intent action).
Awesome!
Edit: It works well by the way.
Working pretty well :thumbup:
Love that you incorporated the ability to have both cap buttons and led blink together.
Nice job!
Sent from my LG-E970 using xda app-developers app
Works great, for me it hasn't been killing my battery, and makes the notification light usable. Only thing that slightly bothers me is that the notification light doesn't smoothly pulse, but that's a small price to pay.
Great job.
milkyline said:
Only thing that slightly bothers me is that the notification light doesn't smoothly pulse, but that's a small price to pay.
Click to expand...
Click to collapse
I'm pretty sure setting the red led to anything greater than 0 sets the led to pulse. To get smooth pulses, adjust the on times. I'd start with 3 seconds and adjust from there.
Sent from my LG-E970
Since I use the Diztrinuc case, which blocks the power button, this app is indispensable. Thanks for putting it together! This works great to enable the front button lights as notification lights.
Sent from my LG-E970 using XDA Premium HD app
Thanks, seems to be working quite well! I have a couple of feature requests, but I don't know how feasible they are.
1. Is it possible to light each of the buttons separately, or can they only be controlled as a single unit? It would be nice if we could assign each button to a specific notification. For example, light the "home" button for texts, the "back" button for emails, etc. It would somewhat make up for the fact that our LED is only a single color.
2. Can you add an option that makes unlocking the phone stop the pulsing, regardless of whether or not the notification was checked?
Sent from my LG-E970
hassa9 said:
Thanks, seems to be working quite well! I have a couple of feature requests, but I don't know how feasible they are.
1. Is it possible to light each of the buttons separately, or can they only be controlled as a single unit? It would be nice if we could assign each button to a specific notification. For example, light the "home" button for texts, the "back" button for emails, etc. It would somewhat make up for the fact that our LED is only a single color.
2. Can you add an option that makes unlocking the phone stop the pulsing, regardless of whether or not the notification was checked?
Sent from my LG-E970
Click to expand...
Click to collapse
I'm glad it's working well! Also, no one has told me any bugs, which means that I made it flawless--doubtful--or, any issues are small. Either way, I'm fine .
I had thought about the individual control, but I'm pretty sure they are all connected. So, to my knowledge, that is not possible.
I like your 2nd idea! I'll work that into the next release. I'll probably release something new soon (likely, this weekend) that is a big re-work of the whole thing. I'm trying to add the option to have the notification stay on as long as it is charging (so it won't timeout), as well as have it stop if the battery is below a certain percentage. I've also fixed the Google Talk notification. I haven't been able to find a different way to get the screen to wake up momentarily without the use of Secure Settings. Personally, I don't think it's a big deal, but it's probably preferable to not need to download a second app--even if it is free. I'll bug GermainZ some more to see if he has any ideas for me .
Almost had a bug for you. Figured out it was the permanent on option lol Nice work.
Btw, that wakelock issue that we talked about hasn't reappeared :thumbup:
Sent from my LG-E970 using xda app-developers app
hassa9 said:
Thanks, seems to be working quite well! I have a couple of feature requests, but I don't know how feasible they are.
1. Is it possible to light each of the buttons separately, or can they only be controlled as a single unit? It would be nice if we could assign each button to a specific notification. For example, light the "home" button for texts, the "back" button for emails, etc. It would somewhat make up for the fact that our LED is only a single color.
2. Can you add an option that makes unlocking the phone stop the pulsing, regardless of whether or not the notification was checked?
Sent from my LG-E970
Click to expand...
Click to collapse
#2 a million times over! I;'ve noticed that even accessing my messages after I get a notification will not stop the notification. I have to go into my status bar and click the ONN icon in order for the pulsing to stop. Sometimes, this can go on FOREVER without me knowing it and my battery just decides to crap out.
The program is awesome tho!! Just would like that feature.
I have a feature request. Can you make it where the light does not come on for charging. I keep it plugged in so it keeps pulsing and I always think I have a notification. Thank you
Sent from my LG-E970 using xda app-developers app
mws1986 said:
I have a feature request. Can you make it where the light does not come on for charging. I keep it plugged in so it keeps pulsing and I always think I have a notification. Thank you
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I like that idea as well. I had tried something to get that last week, but couldn't get it to work reliably. I'll definitely keep trying and include it in one of the next releases if/when I figure it out.
Keep the requests coming! I'll do what I can. Although Tasker is awesome, it does take some time making apps on a phone screen.
CapnPez said:
I like that idea as well. I had tried something to get that last week, but couldn't get it to work reliably. I'll definitely keep trying and include it in one of the next releases if/when I figure it out.
Keep the requests coming! I'll do what I can. Although Tasker is awesome, it does take some time making apps on a phone screen.
Click to expand...
Click to collapse
Well do what you can. You have already done more than I could do. This is a great app and I'm looking forward to see where its headed. Thank you
Sent from my LG-E970 using xda app-developers app
Globalrebel said:
#2 a million times over! I;'ve noticed that even accessing my messages after I get a notification will not stop the notification. I have to go into my status bar and click the ONN icon in order for the pulsing to stop. Sometimes, this can go on FOREVER without me knowing it and my battery just decides to crap out.
The program is awesome tho!! Just would like that feature.
Click to expand...
Click to collapse
I'd also like to see this implemented, if possible. Otherwise, I'll keep saying it, this is a very very VERY useful app. Thanks again for the work!
The app seems to be going haywire on my phone. I've re-installed it a few times now. It will work fine for a day then the led doesn't blink when I get a notification and the battery use for ButtonLED jumps up to around 60%. Any ideas?
johnbyebye said:
The app seems to be going haywire on my phone. I've re-installed it a few times now. It will work fine for a day then the led doesn't blink when I get a notification and the battery use for ButtonLED jumps up to around 60%. Any ideas?
Click to expand...
Click to collapse
That's interesting. What settings do you have on the app? Do you have any other Tasker profiles running? Each time you re-install, you'll need to re-enable the Accessibility as well.
On the version I'm working on now, I'm trying a method to reduce battery usage by disabling the profiles that look to see if one of the apps that generate a notification (Gmail, Voice, etc.) is open (and thus clear the notification) when there is no notification. That way, it won't be polling the apps when it doesn't need to. I'm not sure if that will have much of an impact.
However, I haven't ever seen my battery usage jump up that high (usually, it stays below 4% for me--but I usually clear my notifications fairly soon after they come). Are you using my app (ONN) or GermainZ's (ButtonLED)? I would recommend not using both at the same time.
CapnPez said:
That's interesting. What settings do you have on the app? Do you have any other Tasker profiles running? Each time you re-install, you'll need to re-enable the Accessibility as well.
On the version I'm working on now, I'm trying a method to reduce battery usage by disabling the profiles that look to see if one of the apps that generate a notification (Gmail, Voice, etc.) is open (and thus clear the notification) when there is no notification. That way, it won't be polling the apps when it doesn't need to. I'm not sure if that will have much of an impact.
However, I haven't ever seen my battery usage jump up that high (usually, it stays below 4% for me--but I usually clear my notifications fairly soon after they come). Are you using my app (ONN) or GermainZ's (ButtonLED)? I would recommend not using both at the same time.
Click to expand...
Click to collapse
Um...oops. I just realized I posted this in the wrong app thread, haha. I'm using GermainZ's. Apologies. I haven't had my coffee yet. :silly:
johnbyebye said:
Um...oops. I just realized I posted this in the wrong app thread, haha. I'm using GermainZ's. Apologies. I haven't had my coffee yet. :silly:
Click to expand...
Click to collapse
No problem (I'm glad it's not something wrong with my app!). I hope you get it sorted out. However, you could see if using my app makes any difference (although GermainZ is a lot more experienced than I am, so the likelihood of mine working and his not isn't all that great ). Also, did you re-enable Accessibility after your re-installation of his app? I'm pretty sure every time you uninstall something, it clears that and you would need to re-enable when you install it again.
CapnPez said:
No problem (I'm glad it's not something wrong with my app!). I hope you get it sorted out. However, you could see if using my app makes any difference (although GermainZ is a lot more experienced than I am, so the likelihood of mine working and his not isn't all that great ). Also, did you re-enable Accessibility after your re-installation of his app? I'm pretty sure every time you uninstall something, it clears that and you would need to re-enable when you install it again.
Click to expand...
Click to collapse
Thanks. I did enable Accessibility each time. I switched to your app but I'm still having issues. These apps really don't like me, haha. Maybe something is conflicting? I'm not sure. My app settings are attached and here is a video of what happens:
EDIT: I don't have ButtonLED installed at the same time just fyi.
http://youtu.be/sLLcNmVi2RQ
The LED stops blinking and then the duration changes to something else.
Saw a similar thread for Note II and thought it would be great to see what's going on here. I'm still trying to figure Tasker out but I know its powers are awesome. I learn by seeing and doing. Hope to see some great examples. Thanks!
{
"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"
}
Here are my current tasker profiles.
First two turn data on or off if screen on or off.
Next one lowers cpu and governor with screen off.
Next three adjust cpu and governor based on battery level
Last one jacks up everything while plugged in to a power source.
simoncinis said:
Here are my current tasker profiles.
First two turn data on or off if screen on or off.
Next one lowers cpu and governor with screen off.
Next three adjust cpu and governor based on battery level
Last one jacks up everything while plugged in to a power source.
Click to expand...
Click to collapse
Nice. I love BEAST MODE. I'm trying to learn Tasker without much success so far.
I think I put this thread in the wrong place. Apologies.
toenail_flicker said:
Nice. I love BEAST MODE. I'm trying to learn Tasker without much success so far.
I think I put this thread in the wrong place. Apologies.
Click to expand...
Click to collapse
Well I'm sure there isn't anything wrong with it being here. I know a bit about Tasker, but by no means am I an expert. If you have any specific questions though, I may be able to help out.
My best (and only) tasker profile is one that makes a nandroid each night using the onandroid script
CNexus said:
My best (and only) tasker profile is one that makes a nandroid each night using the onandroid script
Click to expand...
Click to collapse
That's a worthwhile script. I need to make a couple myself.
HAHA
Hello,everybody.I'm new here.And there are always something wrong with my Samsung mobile.I hope we will have a good time here.:laugh:
My profiles are all time based. almost all based around my workday.
Ex. After 10pm until 8am, I have all sounds and alerts off except for ringer.
During day, I use WIFI and BT, normal sounds
On weekends I only use WIFI, but no BT no GPS and different ringtones.
When on power (AC) I have all on WIFI, BT, GPS and a brighter screen.
and I have a group of tasker profiles for my Pebble smartwatch.
I have an On Call profile that has special alerting triggered that takes priority over other things based on calendar info.
Tasker is what you make it. It's well worth learning to use as you can automate most things.
Compusmurf said:
My profiles are all time based. almost all based around my workday.
Ex. After 10pm until 8am, I have all sounds and alerts off except for ringer.
During day, I use WIFI and BT, normal sounds
On weekends I only use WIFI, but no BT no GPS and different ringtones.
When on power (AC) I have all on WIFI, BT, GPS and a brighter screen.
and I have a group of tasker profiles for my Pebble smartwatch.
I have an On Call profile that has special alerting triggered that takes priority over other things based on calendar info.
Tasker is what you make it. It's well worth learning to use as you can automate most things.
Click to expand...
Click to collapse
Can you post your Pebble watch profiles/Tasks
Compusmurf said:
My profiles are all time based. almost all based around my workday.
Ex. After 10pm until 8am, I have all sounds and alerts off except for ringer.
During day, I use WIFI and BT, normal sounds
On weekends I only use WIFI, but no BT no GPS and different ringtones.
When on power (AC) I have all on WIFI, BT, GPS and a brighter screen.
and I have a group of tasker profiles for my Pebble smartwatch.
I have an On Call profile that has special alerting triggered that takes priority over other things based on calendar info.
Tasker is what you make it. It's well worth learning to use as you can automate most things.
Click to expand...
Click to collapse
Thanks. Great info. I'm really struggling with Tasker but won't give up. Busy with work right now. I'll get back on it when the holidays are over.
genevievedewey said:
Hello,everybody.I'm new here.And there are always something wrong with my Samsung mobile.I hope we will have a good time here.:laugh:
Click to expand...
Click to collapse
Hey! The forum and all the help is amazing.
I am glad you started this thread. Tasker is not entirely simple to use when setting up complicated functions and my noobness only bought it yesterday so I could use the help along with a few others I am sure.
Thanks for prior info & in advance.
Sent from above.
Anyone here willing to help me learn tasker. . I just can't seem to figure anything out.
Was trying to do the hi galaxy s voice thing but all the instructions say are create a profile with this
Context -> S-voice is open
Action -> Go Home 0, Open "Voice Search"
But for the life of me I cannot figure this out
Ple as e he lp
Sent from my SM-N900P using Xparent Purple Tapatalk 2
1) I made a script that puts my phone on silent when it's face down.
2)I have another one that automatically opens google music when I use my headphones.
3) I also have a profile that takes pics when I flick my phone like on the Motorola X
Sent from my SM-N900P using xda app-developers app
shadow77048 said:
1) I made a script that puts my phone on silent when it's face down.
2)I have another one that automatically opens google music when I use my headphones.
3) I also have a profile that takes pics when I flick my phone like on the Motorola X
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Mind sharing that last one?
Looking to make a TASKER profile
alright since this is kinda a thread that might answer this question, I need some info, so I'll ask if somebody can help me with setting up the following.
I need a profile setup for Tasker that sets my wallpaper based on whether I'm at work or not based off of whether or not there's a WORK event on my calendar and what time that event happens. (I work at a Sprint store and I need to make sure that my wallpaper is more "customer friendly" during my shifts and can go back to what I want it to be when not.)
If anybody can give me some pointers as to how to do this, I'd be your friend for life. Or at least until you can't answer a question, whichever comes first.
Since someone asked me to share my flick phone to take a picture (like moto x) profile you have to adjust sensitivity to your preference
Sent from my SM-N900P using xda app-developers app
I have a few pretty simple tasks setup:
Profiles:
Night Mode
Triggers: power AC , time: 23:45 - 7am connected to home wifi
entry task: Night Mode ( SMS Backup, Silent Mode, Lampshade sunset,Auto Brightness Off, Display Level 0)
Description:Backup all new SMS using smsbackup+ perform a "sunset" using the Philips Hue lightbulbs I have in the bedroom and put the screen brightness to extremely dim.
exit task: Night Mode end ( auto brightness and silent mode set to off)
Morning Sunrise
Triggers: Alarm Done, connected to home wifi, time 6am - 11am
entry Task: Sun Rise (lampshade sunrise)
description: when a phone alarm goes off first thing in the morning whilst at home perform a "sunrise" effect with the Philips Hue lightbulbs in the bedroom.
Silent In Lectures
Triggers: calendar entry at my university address.
Entry Task: Silent Mode On
Exit Task: Silent Mode off
planning on adding a few more useful things, but the ones that I have seem quite nice.
I have a ton of tasker tasks setup mostly having to do with the lights in my house (all with voice commands, ex: turn on christmas lights, turn off kitchen light, etc), but some others are to directly call contacts without waiting for google to confirm who the contact is and so on and so forth, start playing any random netflix video i'd like to watch with voice command, start the sonos sound system in my house with voice command, make my phone ring when i lose it by sending a text containing a certain string of text from any other device/phone, turning my hotspot on automatically when connected to the bluetooth in my car, when disconnecting the bluetooth it auto shuts off the hotspot, switching my notifications on my smartwatch on when a certain string of text is sent to the phone.
On my tablet that i have as my entertainment system in my car i have tasker as well and as soon as it connects to the hotspot from my phone it automatically starts recording my drive with video, than opens google music and starts playing my music, than opens waze. When the wifi connection to my phones hotspot is gone it turns everything off on the tablet and just sends it back to the homescreen.
One task im still trying to get going is the ability to turn on and off the television which i've seen before just cannot seem to find the module i need to do it, since i dont want to use the same i'd use for lamps afraid it will burn out the tv and not work properly.
I just started playing around with tasker yesterday. Coming from Llama, I found that it takes longer to learn tasker but the rewards were so much greater. Here are two profiles that might be useful for others too.
The first one is to reject a call from my gf and create a button on the screen so I can call her back on my unlimited plan.
I included a vibration pattern there so I can get some sort of alert going on after the incoming call is rejected. You can of course add a ringtone there as well.
use a phone ring event to trigger following task:
https://www.dropbox.com/s/tbgjtewdebdnitn/Ring_Back_DM.tsk.xml
https://www.dropbox.com/s/vkxxbpjqoc07uiv/Call_Dm.scn.xml
The first file is the task, the second one is the scene that creates the button to call back. You will need to edit that 2nd file to add your own number to call, just look for ###replace### in that file.
To dismiss the button without calling back, just tap and hold it.
Another task I made after I saw somebody mentioned about displaying current address in Dashclock. This one involves google map geocode api and a little javascript.
To conserve battery, this only shows you a rough address. If you need accuracy, you can add a action at the start to turn on GPS for say 30-60 seconds.
Also If you want to use the address somewhere else instead of showing up in Dashclock, just replace the last action with your own. BTW, you need to install Dashclock tasker extension before running this task(if you're keeping the last action).
Use a cell ID variable set event to trigger this task:
https://www.dropbox.com/s/15fsvwhecb83utz/Current_Address.tsk.xml
**** 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.
My last phone before this one is the Droid Mini. So far the Z5C is infinitely better in everything (but my expectations/standards are pretty low...) except that the Active Display feature from Motorola was awesome. From a bit of Googling, there are some other apps that copy this functionality to various degrees, but maybe some of you can give more specific insight than the articles?
1.) First of all, I'm confused. This article below states that Motorola released the app on Google Play Store for the general Android population... but it doesn't come up when I search it on my Z5C. What the hell?
http://gadgetstouse.com/featured/to...lay-notifications-alerts-android-device/19901
2.) If the Moto app is not available, any opinions on the alternatives? From reading a few articles, sounds like Dynamic Notifications is my best bet. Thoughts?
I tried xposed module, but it used proximity sensor, so it is not the same thing. I also miss that feature a lot from my nexus 5x, double tap to wake is kind of replacement when phone is laying on the table. When you take it out from a pocket, pressing the button isn't such a big deal. I couldn't find any reasonable replacement so I learnt to live without it
I really don't understand why other manufacturers don't copy-cat this feature. It was without question the greatest feature of my old phone.
I tried out Dynamic Notifications, but it's weird. First, it didn't play nice with the existing lock-screen and login structure. When I had a notification, pressing the power button no longer took me to the lock screen -- instead it just turned off and locked the screen. It's as if Dynamic Notifications became a second lock screen, and the power button toggled it on/off, and I had to tap the home key to get to the actual lock screen. On top of that, after getting to the actual lock screen it seemed to somehow screw up the fingerprint login because I kept getting prompted to use my other login method (PIN in my case). Most weird of all, it had some crazy bug when I used Uber. I was trying to check where the Uber car was on the map, and it threw me to the Dynamic Notifications screen, with the Uber notification showing. I logged in again, pulled up Uber again, checked the location of the Uber on the map, and it instantly did it again! And again... So screwed up.
TL;DR: Do not use this app, at least not on this phone. It's buggy and/or just makes you jump through extra hoops when logging in.
Yeah I also have double tap enabled. It's okay I guess.
Nexus 5x had a dedicated hardware sensors for that matter, I guess that may be the problem. Anyway I agree with you that every manufacturer should implement it.
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
try use ambient display is an xposed module
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
So I finally got around to trying out AcDisplay. That video that is on the app download page shows how you can wake up the phone using proximity sensors, when pulling it out of your pocket or even waving your hand over it... But none of this works at all. Not even a little bit. Does that mean that the Z5C does not have any proximity sensors built into it?
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.