[APP] SideSqueeze 2.08 - add squeeze gestures to your S10+! - Samsung Galaxy S10+ Themes, Apps, and Mods

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"
}

I like the concept of the app but I tried it and it is very difficult to use coming from a pixel device. I set up custom squeeze pressures but it won't work properly. A squeeze will usually engage what I want but if I move phone around or sit it down it will also do the squeeze action. Good idea but going to be tough to do properly i feel!

oneandroidnut said:
I like the concept of the app but I tried it and it is very difficult to use coming from a pixel device. I set up custom squeeze pressures but it won't work properly. A squeeze will usually engage what I want but if I move phone around or sit it down it will also do the squeeze action. Good idea but going to be tough to do properly i feel!
Click to expand...
Click to collapse
Thank you for your feedback. Have you calibrated it? What are your gain and release threshold set to? What sensitivity level are you using?

ffolkes said:
Thank you for your feedback. Have you calibrated it? What are your gain and release threshold set to? What sensitivity level are you using?
Click to expand...
Click to collapse
I did it kept saying try again and changed values, said like 50 try again then 100 then -10 and kept saying try again. It was really odd

Same here.... S10+..... Seems difficult to get out of the calibration stage. Then, sometimes the squeeze works and sometimes it does not. I also see calibration messages after exiting the app.
Interestingly, the squeeze command seems to always work when in the app.
When I retried to calibrate with a squeeze command already set, the command activated and the assigned app launched.
Will try to play with it again later.
Sent from my SM-G975U using Tapatalk

Now I am getting a notification that side squeeze is running. However, I have had it disabled in the app!
Sent from my SM-G975U using Tapatalk

dctrbnsttr said:
Same here.... S10+..... Seems difficult to get out of the calibration stage. Then, sometimes the squeeze works and sometimes it does not. I also see calibration messages after exiting the app. Interestingly, the squeeze command seems to always work when in the app.
When I retried to calibrate with a squeeze command already set, the command activated and the assigned app launched.
Will try to play with it again later.
Click to expand...
Click to collapse
This is really weird, and no one has ever reported behavior like this. I can't seem to reproduce it. Was there any step that stood out in your mind? Did you do anything unusual? Do you remember roughly what the message said? There are only a few it could have been, any words or phrases you remember from it? Thanks!
The time you tried to calibrate with a command set, did you remember if you tapped the "Start" button at the bottom first?
dctrbnsttr said:
Now I am getting a notification that side squeeze is running. However, I have had it disabled in the app!
Click to expand...
Click to collapse
Is it possible you have the press detection module on? The engine stays running unless both are disabled. Open the left fly-out menu and go to Screen Presses and make sure that is off, too.

ffolkes said:
This is really weird, and no one has ever reported behavior like this. I can't seem to reproduce it. Was there any step that stood out in your mind? Did you do anything unusual? Do you remember roughly what the message said? There are only a few it could have been, any words or phrases you remember from it? Thanks!
The time you tried to calibrate with a command set, did you remember if you tapped the "Start" button at the bottom first?
Is it possible you have the press detection module on? The engine stays running unless both are disabled. Open the left fly-out menu and go to Screen Presses and make sure that is off, too.
Click to expand...
Click to collapse
Unfortunately, I don't recall the text of the toast message. Yes, I clicked on the start button to calibrate. As far as I know, I did nothing unusual. Press screen was turned off.
I just now opened the app, made sure that both screen pressure and squeeze were not enabled. After exiting the app, there is a notification that sidesqueeze is running.
Also, there is an issue with the discord server. I have to open the sidesqueeze app and click on the discord link to open it. I accept the invite. 5 minutes later, the server disappears from the discord app. When I tried to join again thru the discord app, it states that the invite has expired. This is repeatable.
Sent from my SM-G975U using Tapatalk

I got working a little bit, took literally 5 mins to setup though. It's hit or miss now though works maybe 50% of the time and still sometimes randomly

I deleted cache and data. I installed the new test version you sent. It seems to be much more stable and working as it should. I will give it more time to see if all remains well.
Sent from my SM-G975U using Tapatalk

This is new and useful for S10+! Nice app my man! Thanks!

After using the new build a bit more, a couple of observations. First, the action set for one squeeze, sometimes activates without me squeezing the phone. Secondly, with sidesqueeze activated and the press actions definitely switched off, I can no longer double tap to wake my s10+. As soon as I deactivate sideswitch, double tap to wake is restored.
Sent from my SM-G975U using Tapatalk
---------- Post added at 08:55 PM ---------- Previous post was at 08:29 PM ----------
Also, unfortunately, the notification that sidesqueeze is running even when neither squeeze or press is enabled, is back...... This after the playstore update to version 201.
Sent from my SM-G975U using Tapatalk

dctrbnsttr said:
After using the new build a bit more, a couple of observations. First, the action set for one squeeze, sometimes activates without me squeezing the phone. Secondly, with sidesqueeze activated and the press actions definitely switched off, I can no longer double tap to wake my s10+. As soon as I deactivate sideswitch, double tap to wake is restored.
---------- Post added at 08:55 PM ---------- Previous post was at 08:29 PM ----------
Also, unfortunately, the notification that sidesqueeze is running even when neither squeeze or press is enabled, is back...... This after the playstore update to version 201.
Click to expand...
Click to collapse
I have no idea about the double tap thing, I'll have to look into it. As for the notification, when does it come back?

The double tap may have had something to do with the aod..... The notification returned after I rebooted the phone.
Sent from my SM-G975U using Tapatalk

dctrbnsttr said:
The double tap may have had something to do with the aod..... The notification returned after I rebooted the phone.
Click to expand...
Click to collapse
Oh ok, that's actually fixed in the last minute update I pushed out moments after 2.01. It should be rolling out to you any minute now.

I have been noticing that if I set the squeeze strength to custom rather than to soft or medium for example, sidesqueeze resets itself to medium.
Sent from my SM-G975U using Tapatalk

dctrbnsttr said:
I have been noticing that if I set the squeeze strength to custom rather than to soft or medium for example, sidesqueeze resets itself to medium.
Click to expand...
Click to collapse
Thanks for the feedback, as always. Can you reproduce this? When does it happen? Like, does it only reset when the app opens? What were you doing before it reset? Is 'Firm' affected, too?

ffolkes said:
Thanks for the feedback, as always. Can you reproduce this? When does it happen? Like, does it only reset when the app opens? What were you doing before it reset? Is 'Firm' affected, too?
Click to expand...
Click to collapse
Can't pinpoint any specific event or time. Haven't used firm at all. Also noticing that sometimes it seems overly sensitive and other times it won't respond at all. I will try to notice when these things occur.
Sent from my SM-G975U using Tapatalk

Version 2.04 is ready for testing:
Improvements to the algorithm
More responsive
Added Long Double-Squeeze
Multi-squeeze delay is now adjustable
Fixed bug in Quadruple Squeeze
UI improvements and fixes
Crash fixes
Download

Trying it out.... Will see how it goes
Has been running for an hour or so.... Seems much more consistent and stable thus far....
Sent from my SM-G975U using Tapatalk

Related

[APP][ROOT][1.6+] ButtonLED v1.6 (05/05/13)

I'm not planning to update this app anytime soon. You can try alternatives if you want, such as Backlight & Sound Notification. Thanks.
Read the FAQ before asking questions. If you haven't read it, my only reply will be "Does the FAQ help?"
Click to expand...
Click to collapse
You do NOT need a kernel with BLN support to use this app. In fact, I made this because my device has no BLN kernels.
Also, a quick note for those who are gonna read the comments: The attached MDPI/HDPI versions look fine on respective devices. The first version of ButtonLED was only available for MDPI, which should explain the first few comments.
Hey guys,
I've been fiddling around Tasker for the last few weeks and finally decided to create a fully functional app using it.
At this point, some of you will be thinking "another useless, ugly, cluttered Tasker created app that does something nobody needs".
Well, then, I'll try to prove you wrong
You do NOT need Tasker to use the app.
App Description:
ButtonLED is similar to NoLED: It allows you to have led like notifications without actually having the led light. However, NoLED uses uses your screen; ButtonLED only uses the hardware buttons' backlight (your screen stays off). It's customizable to an extent, with more to come depending on feedback and suggestions.
Features:
status bar notifications + missed call/unread text support;
pause for some user defined time on proximity (e.g. If phone is turned down, or is in your pocket);
turn button backlight for x seconds, then off for y seconds;
notification exceptions (e.g. To ignore all notification that contain "hello", add *hello* to the exception list);
logs;
should work on all devices since the user can locate the brightness file;
and some more (check the screenshots, install the app).
Compatibility:
It should work on all rooted devices (some devices have a kernel level limitation; read the FAQ). At the moment, you'll also need to have a proximity sensor to run it. It should work without having to do (almost) anything manually for many devices. If auto locate doesn't find anything useful, you'll have to manually locate the brightness file. Please share the results when you do that so i can improve the auto locate feature.
Running The App:
install and open the app. You should be greeted by a popup showing you a list of files. Select the most appropriate (you're looking for something that has a path such as "/sys/devices/platform/bcm21553-leds/leds/button-backlight/brightness). Once you're done, click "enable buttonled in accessibility" and do so. Come back to buttonled and tap the "test buttonled" button. If your capacitive buttons flash, you're good to go. Otherwise, you will need to select a different brightness file (use auto locate or do it manually).
You may also want to customize the options.
Some examples for the brightness file:
Code:
I'll update this list later.
Auto Locate will not follow symlinks as it can cause infinite loops or imprecise results (if it doesn't search deep enough). Usually, /sys/class/leds will have symlinks to all LEDs, backlight included. Check it out.
Screenshots (actual release is slightly different):
{
"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"
}
Changelog:
v1.6 (05/05/13):
You can now ignore apps as well.
The battery tweak can be disabled on devices where ButtonLED was flashing the LEDs once or twice before sleeping forever.
You can long press log items to view the full text, for items that didn't fit.
Proximity sensor feature is now disabled (it wasn't working anyway due to a Tasker limitation) (the UI option is still listed as "FEATURE DISABLED"). This should have a minor but positive impact on performance/battery.
Minor UI changes.
Other minor changes.
v1.5 (24/02/13):
Wake locks are released while the LEDs are off and ButtonLED is waiting;
Sleep timer is fixed. The current value is also displayed when changing the sleep start/end times;
Tapping on a log entry will give you the option to add that notification to the exclusion list;
ButtonLED will give you the choice to install Busybox if it's not found;
File Browser/Auto Locate issues might be fixed for users who were having them (pressing File Browser did nothing at all even if Busybox is installed). Please try it if you were having this issue.
Added XHDPI version for everyone. Also added MDPI for JB/CM10 users.
v1.4 (19/01/13):
Manual search is now as fast as other file explorers (busybox is required);
Sleep start/end added (ButtonLED will not react to notifications during that time);
Confirmation added before removing exceptions;
Fixed a (rare?) issue where ButtonLED kept blinking the lights after the screen is turned on;
Might be more battery efficient if using higher LED Off delays, not sure. But if it is, it will be much better (more testing needed);
v1.3.1 (03/12/12):
ButtonLED will stop notifying you about missed calls and unread texts when you turn your screen on, instead of continuing till you view them;
Auto Locate will now simply search /sys for the brightness file. That means it will locate more files, across more devices. It's also faster;
Fixed the bug where ButtonLED would forget resuming once the battery drops below the threshold then go above it again.
v1.3 (03/11/12):
Stop service and exit menu option;
Ignore notifications if battery is lower than threshold;
Fixed exceptions not taking effect;
Changed the path auto locate looks into. Hopefully, this will make it work for more devices;
Two versions are now available, one for mdpi devices, the other for hdpi devices (thanks for .xxx. for testing).
v1.2 (27/10/12):
Rewrote most of the logic;
Better handling of events;
Less battery consumption and more accurate logs;
Logs now show battery percentage on processed notifications, screen on (if notifications are pending) and device shutdown, which should give users an idea about battery consumption;
Fixed logs showing skipped notifications as processed (e.g. Notifications that were issued with the screen turned on were skipped but shown as processed in the logs);
Auto Locate brightness file option (beta; need more device specific info to tweak the search);
Separated missed call from unread text notifications;
Run with higher task priority, should avoid lag (uses the renice linux shell command).
v1.1 (24/10/12):
Missed call/unread text notifications support;
Optional permanent notification;
Option to use flashlight instead of the hard buttons' led light;
Test button that will turn on and off the led/flashlight;
Other minor modifications and fixes.
(original beta thread)
To Do:
Landscape support;
Patterns?
This list is updated based on your feedback. Want to see a feature? Suggest it!
Bugs:
Proximity sensor doesn't have any effect;
This list is updated based on your feedback. Thanks for reporting any bug you find.
Downloads:
Don't forget to post your comments!
Get ButtonLED
Jelly Bean/CM10 users, get the "ButtonLED.x.x.XXXX_JB.apk".
Everyone else, download "ButtonLED.x.x.XXXX.apk".
Don't know which APK to grab? Read the FAQ for info on how to determine your resolution (MDPI, HDPI, XHDPI, ..).
You can find previous versions here.
Tasker Project:
You can get the Tasker project if you prefer, it offers the same functionality but will run inside Tasker instead of being a separate app.
You need Tasker (pre-ICS versions only) and the Holo Light IPack icon pack to use this.
Grab the appropriate project file from here.
Place the XML file in your SD Card (e.g. mnt/sdcard/tasker/projects/) and open Tasker. Long tap on an existing project (if you can't see the projects bar, disable beginner mode in Tasker's settings, then swipe down from the "projects"/"tasks"/"scenes"/"variables" bar), select "import", then tap on the file's name (e.g. buttonled.hdpi). You should see a new project appear with ButtonLED's icon. Apply the changes by tapping on the green check mark in the bottom left corner, then open Tasker again.
To open ButtonLED's configuration menu, run the task named "config".
Click to expand...
Click to collapse
~~~~
FAQ:
Q: It's not detecting my brightness file!
A: Apparently, if you have a kernel with BLN support, you don't have one. Otherwise, try searching manually or asking on your device's forum. And to make sure auto locate didn't miss something, you can run this in a terminal emulator (this will also expand the search so expect some weird results):
Code:
find / | grep brightness
It's worth noting that Auto Locate will not follow symlinks as it can cause infinite loops or imprecise results (if it doesn't search deep enough). Usually, /sys/class/leds will have symlinks to all LEDs, backlight included. Check it out.
Q: The test button works fine, but ButtonLED won't react to my notifications.
A: make sure ButtonLED is enabled in accessibility. Also, check ButtonLED's logs. Is it detecting the notifications? Is it reacting to them, but you fail to see it? If that's the case, try increasing the led on duration.
Q: Can i use this with application xyz (e.g. Whatsapp)?
A: if the application sends notifications, yes. ButtonLED will automatically detect them.
Q: Should i get the MDPI or HDPI APK?
A: if your device's density is ~160, get the MDPI APK. If it's ~240, download the HDPI APK. If you don't know, download an app from the market that will show you (e.g. screen resolution), or grab the MDPI APK and if it looks squished, uninstall it then install the HDPI APK.
Q: Battery usage is too high!
A: ButtonLED will hold a wakelock when it's flashing the LEDs. Configure it to ignore notifications you don't care about (turn the logs on, and use exceptions). See this post.
Q: Auto Locate/File Browser isn't working!
A: Try installing Busybox.
Also make sure ButtonLED has root permissions - check your SU app, and try to revoke permissions then give them back.
If that fails, it might be related to how Tasker checks if your device is rooted:
Tasker decides that a device is rooted if /system/app/Superuser.apk is present and su is present in one of the directories of $PATH
Click to expand...
Click to collapse
Q: Test works, and the logs show that ButtonLED detects and processes my notifications, but it won't light my LEDs!
A: Check this out.
Q: Talkback is talking randomly even when I have it disabled!
A: That's a known Samsung issue. It's not related to ButtonLED.
Q: How do I ask for help?
A: What have you tried? Did you do anything covered in this FAQ but it didn't help? Have you read the last few pages of comments? If you don't answer any of these questions, I'll assume you haven't read this FAQ and my reply will be "Read the FAQ".
Click to expand...
Click to collapse
~~~~
Reserved
fantastic concept, but the lights flash all the time, without notifications, on my mother's lg p500!
i'll keep watching you for updates, and i'll be testing =)
thanks!
joaor10 said:
fantastic concept, but the lights flash all the time, without notifications, on my mother's lg p500!
i'll keep watching you for updates, and i'll be testing =)
thanks!
Click to expand...
Click to collapse
The logs should be useful in that case. Did you check them out? It might be because of another app that has a permanent notification (e.g. Tasker).
edit: did auto locate work for you? If not, where was your brightness file?
I just noticed the exceptions aren't taking effect (forgot a line ). It's fixed in v1.3, will upload it later.
Regarding resolutions, I'll try checking the XML files later and try adapting it to all resolutions. Don't hold your breath, tho. Worst case scenario, multiple versions will be created, one for each resolution.
If you know where a device's brightness file is located (perhaps you own it, or you just read it somewhere), please share so I can improve the auto locate feature.
Thanks.
will there ever be a compatible jb version?
So in other words, it's like Backlight Notification but for all phones?
https://play.google.com/store/apps/details?id=neldar.bln.control.free
Exploitlol said:
will there ever be a compatible jb version?
Click to expand...
Click to collapse
If anyone has Tasker and can generate JB APKs ("Minimum Android Version: 16" setting) without problems, I'll be happy to pass the project for them to export and send me back, after which I'll upload it.
polobunny said:
So in other words, it's like Backlight Notification but for all phones?
https://play.google.com/store/apps/details?id=neldar.bln.control.free
Click to expand...
Click to collapse
Pretty much, although it works differently: BLN "redirects" LED notifications to the capacitive buttons, ButtonLED tries to detect all notifications.
It's more like NoLED but with capacitive buttons.
Thanks GermainZ...Working on my Ace-i
How's the battery drain?
ccab said:
How's the battery drain?
Click to expand...
Click to collapse
I did my best to keep as low as possible: the sensor is only checked when the notification is triggered and every 30 cycles after that.
I did some testing and the drain was around 6.5% per hour on my device (tested for around 7 hours). Note that was before I fully implemented the battery saving features, so it will probably be less. The used settings were: 1s on, 1s off. (current default is 1s on / 4s off)
But then again, it all depends on your device. Obviously, having a kernel that supports underclocking (e.g. setting your frequencies to 156Mhz-1Ghz with a governor that doesn't lock the frequency to the max) helps, since your device will always be awake if ButtonLED is active (active as in turning the LED on and off, not just running in the background).
Thanks a tonne man.. I was waiting for such an app for like months now.. glad it came and yeah fyi I have subscribed to the thread and waiting for more features and updates..
Sent from Hell!!
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
Resizing for hdpi phones is needed hehehe..
And May I ask where the brightness file is generally located ? Because I wasn't able to make the app work for some reason :/
Sent from Hell!!
.xxx. said:
Thanks a tonne man.. I was waiting for such an app for like months now.. glad it came and yeah fyi I have subscribed to the thread and waiting for more features and updates..
Sent from Hell!!
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
Resizing for hdpi phones is needed hehehe..
And May I ask where the brightness file is generally located ? Because I wasn't able to make the app work for some reason :/
Sent from Hell!!
Click to expand...
Click to collapse
Autolocate didn't work?
It depends on the device and ROM used, really. In the first post, I posted two examples (S5830 and S5830I).
Judging from your signature, I'm guessing you're using the Galaxy S3. After some googling, I think this file will work:
/sys/class/leds/button-backlight/device/leds/button-backlight/brightness
If not, well... Try asking on your device's forum and report back once you find it
GermainZ said:
Autolocate didn't work?
It depends on the device and ROM used, really. In the first post, I posted two examples (S5830 and S5830I).
Judging from your signature, I'm guessing you're using the Galaxy S3. After some googling, I think this file will work:
/sys/class/leds/button-backlight/device/leds/button-backlight/brightness
If not, well... Try asking on your device's forum and report back once you find it
Click to expand...
Click to collapse
Auto locate did not work man. When I tried the test, it gave me this reason.
My decide is LG optimus sol with cm7.
I would glad to see a reply soon. Eager to make it work.
Sent from Hell!!
.xxx. said:
Auto locate did not work man. When I tried the test, it gave me this reason.
My decide is LG optimus sol with cm7.
I would glad to see a reply soon. Eager to make it work.
Sent from Hell!!
Click to expand...
Click to collapse
Try this:
Tap the "Browse for the button brightness file" button
Go to /sys/class/leds/button-backlight/
Tap the "brightness" file
Test
If that doesn't work, try the same with /sys/class/leds/button-backlight/device/leds/button-backlight/ in step 2.
GermainZ said:
Try this:
Tap the "Browse for the button brightness file" button
Go to /sys/class/leds/button-backlight/
Tap the "brightness" file
Test
If that doesn't work, try the same with /sys/class/leds/button-backlight/device/leds/button-backlight/ in step 2.
Click to expand...
Click to collapse
Man!!!!!! You are a life saver.. Thanks a lot.. I got the file.. tested the button led light.. and now looking forward for real time notification.
Sent from Hell!!
---------- Post added at 12:12 PM ---------- Previous post was at 12:05 PM ----------
Okay. So, here is the deal.
In test mode it works like a charm. But in real time notification, it won't glow the soft key light.
Sent from Hell!!
.xxx. said:
Man!!!!!! You are a life saver.. Thanks a lot.. I got the file.. tested the button led light.. and now looking forward for real time notification.
Sent from Hell!!
---------- Post added at 12:12 PM ---------- Previous post was at 12:05 PM ----------
Okay. So, here is the deal.
In test mode it works like a charm. But in real time notification, it won't glow the soft key light.
Sent from Hell!!
Click to expand...
Click to collapse
Did you enable ButtonLED in Accessibility?
If you did, check ButtonLED's logs. Do note that ButtonLED will only work if your display is off, and will stop notifying you once you turn the screen on.
GermainZ said:
Did you enable ButtonLED in Accessibility?
If you did, check ButtonLED's logs. Do note that ButtonLED will only work if your display is off, and will stop notifying you once you turn the screen on.
Click to expand...
Click to collapse
I have enabled it in accessibility.
Buttonled log looks normal to me. It catches the going processes.
Yeah, the display was off for a long.time and there were missed calls but soft keys never glowed :/
Sent from Hell!!
.xxx. said:
I have enabled it in accessibility.
Buttonled log looks normal to me. It catches the going processes.
Yeah, the display was off for a long.time and there were missed calls but soft keys never glowed :/
Sent from Hell!!
Click to expand...
Click to collapse
What do the logs say
Normally, it would be something like this:
Code:
14:57: Stopped (screen turned on; battery: 87%)
14:56: Sleeping for 300 s (proximity detected; battery: 87%)
14:51: Sleeping for 300 s (proximity detected; battery: 87%)
14:51: Missed Call (processed; battery: 87%)
14:51: Missed Call (detected)
Also try setting a higher "on" delay, just to make sure it's not turned off too fast.

[APP][3.0+] Gliderun *OPEN BETA*

Sports activity tracker
* ALPHA * state.
I'm looking forward for people to test and send suggestions.
Track your sports activities capturing
location
cadence
altitude
power
heart rate
speed
bearing
slope
etc...
Plot progress, lap time and other
Set targets and receive feedback while tracking your session
Works in landscape and portrait
Audio rithmic control.
Reproduce your music at modified tempo to match your cadence.
Enable metronome to help with cadence.
Download or import routes.
Routes export to GPX and KML
Google earth route export *Broken*
Check compass and GPS status
Integration of sensors and wearables
Heart rate and other BTLE sensors.
Miband
Ready to integrate more
Google fit integration
https://play.google.com/store/apps/details?id=com.tincore.and.gliderun
{
"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"
}
IMPORTANT NOTES
The app will only discover wearables like MiBand if they are not used at the same time by another app like MiFit. You need to close MiFit for the band to be discovered.
In the case of the MiBand when you change the app your band stored data will be wiped. I'm investigating a way to avoid this.
What does it do..?
First message updated a bit
How to connect with mi band? I search for devices but it find nothing
Edit: just figured it out
I have a question. After connected to my miband I tapped on the top left settings icon and I saw in the bottom of the list the option "factory reset". Is it really possible? What are the consequences? In the official app this option doesn't exist
Sent with my Nexus 5 through time and space
giorgis91 said:
How to connect with mi band? I search for devices but it find nothing
Edit: just figured it out
I have a question. After connected to my miband I tapped on the top left settings icon and I saw in the bottom of the list the option "factory reset". Is it really possible? What are the consequences? In the official app this option doesn't exist
Sent with my Nexus 5 through time and space
Click to expand...
Click to collapse
To connect the MiBand you unpaired it first from the other app havent you?
The Admin section of wearables exposes all kind of operations. Some of them are rather low level and even should be executed on a particular order. I may hide/show all that under a setting to avoid mistakes.
Factory reset just does that. It will wipe all the pairing data.
tincore said:
To connect the MiBand you unpaired it first from the other app havent you?
The Admin section of wearables exposes all kind of operations. Some of them are rather low level and even should be executed on a particular order. I may hide/show all that under a setting to avoid mistakes.
Factory reset just does that. It will wipe all the pairing data.
Click to expand...
Click to collapse
Thank you for answering quickly I ask that because lot of people on an Italian forum that I know had many problems with this wereable and I thought that a factory reset could solve them.
Another question: after using you're app I noticed that after reconnecting the mi band to its official app all the data was lost. Is it normal?
Sent with my Nexus 5 through time and space
giorgis91 said:
Thank you for answering quickly I ask that because lot of people on an Italian forum that I know had many problems with this wereable and I thought that a factory reset could solve them.
Another question: after using you're app I noticed that after reconnecting the mi band to its official app all the data was lost. Is it normal?
Sent with my Nexus 5 through time and space
Click to expand...
Click to collapse
About the data wipe. This is normal the app is setting new user data based on the personal profile.
Same with the alarms. The band, as far as I know, does not have a way to retrieve the current alarm configuration.
Thanks for the app. I think it very promising. I just installed the app from google play, unpaired the band with mi fit app and connected with gliderun. After connection, it stays short time as connected and disconnects after 4-5 seconds. Is there a reason you can tell? I use smartlock app and I am on cm11.
Thanks again.
saltinbas said:
Thanks for the app. I think it very promising. I just installed the app from google play, unpaired the band with mi fit app and connected with gliderun. After connection, it stays short time as connected and disconnects after 4-5 seconds. Is there a reason you can tell? I use smartlock app and I am on cm11.
Thanks again.
Click to expand...
Click to collapse
Sorry for not answering before. Is it working better now. There have been a good number of versions.
Hey, tincore. Thank you for making the app compatible with the Mi Band! Since there's a lack of feedback here for you, I'd like to leave you some general issues/thoughts/etc. If you'd like to inquire about any of my comments, or would like logs of anything, please let me know and I'll provide that. If you wouldn't mind just quoting some of my comment so I can get an e-mail notification of your reply, that'd be great!
I'm on Android 4.4.4.
- Initially, I had trouble pairing the Mi Band with the app. I unpaired my band from MiFit, killed MiFit, and attempted pairing to Gliderun. Initially, Gliderun would connect to the band, this is where band's lights light up, and you have to tap the band to 'accept' the pairing; but when you tapped the band nothing happened. However, a minute later the band connected to Gliderun as if I tapped it.
- When I connected to Gliderun, it recognized that I had 6,000 steps, but once I began walking, the app started counting from 0.
- I'm kind of confused about the 'start' function on the Activity tab. Am I supposed to have this enabled? Normally, I just go into MiFit, refresh the page for it to download the data from the band. Can I essentially do this with Gliderun without using this start function?
- On the Activity tab, is there a way to make 'empty' cells completely blank?
- Is there a way to track sleep?
Previously, I had trouble getting my MiBand to reliably stay connected with Gliderun, but now it seems to keep the connection fine. I'll start using this app daily instead and I'll check back here with any updates. Thanks again!
Thanks for the remarks!
After the band is paired once the app tries to find and reconnect to it automatically. I imagine that first time there was a problem with the connection so it connected on the retry . It *should* also syncronize itself every 1-2 hours..
About step count and the start button. Gliderun tries to combine activity and general tracking. When you start a particular activity (by clicking on start) it should count the steps of that activity. When you are not in a activity it should count those steps globally for a daily total.
To activate global tracking you can go to preferences > tracking or tap on some of the inactive dashboard indicators. Without global tracking activated you should still see some totals after syncronization with the band.
You have,at least, two steps counters the band and your phone. Each of them has an absolute step count.
"Sensor step counts" indicator shows the steps of the active step counter so depending on the band being connected or not it may toggle to your phone. I hope this makes sense.
I will add a "Blank" indicator asap.
About sleep. The app should be already tracking your sleep periods. You can see those on Global stats screen. I would like to add the deep sleep phases but I need documentation or advise on what exactly I have to look for in order to provide a faithful solution.
I'm trying now to fix a few issues to move to beta. I hope I can make a video and some captures soon.
adobrakic said:
Hey, tincore. Thank you for making the app compatible with the Mi Band! Since there's a lack of feedback here for you, I'd like to leave you some general issues/thoughts/etc. If you'd like to inquire about any of my comments, or would like logs of anything, please let me know and I'll provide that. If you wouldn't mind just quoting some of my comment so I can get an e-mail notification of your reply, that'd be great!
I'm on Android 4.4.4.
- Initially, I had trouble pairing the Mi Band with the app. I unpaired my band from MiFit, killed MiFit, and attempted pairing to Gliderun. Initially, Gliderun would connect to the band, this is where band's lights light up, and you have to tap the band to 'accept' the pairing; but when you tapped the band nothing happened. However, a minute later the band connected to Gliderun as if I tapped it.
- When I connected to Gliderun, it recognized that I had 6,000 steps, but once I began walking, the app started counting from 0.
- I'm kind of confused about the 'start' function on the Activity tab. Am I supposed to have this enabled? Normally, I just go into MiFit, refresh the page for it to download the data from the band. Can I essentially do this with Gliderun without using this start function?
- On the Activity tab, is there a way to make 'empty' cells completely blank?
- Is there a way to track sleep?
Previously, I had trouble getting my MiBand to reliably stay connected with Gliderun, but now it seems to keep the connection fine. I'll start using this app daily instead and I'll check back here with any updates. Thanks again!
Click to expand...
Click to collapse
tincore said:
Thanks for the remarks!
After the band is paired once the app tries to find and reconnect to it automatically. I imagine that first time there was a problem with the connection so it connected on the retry . It *should* also syncronize itself every 1-2 hours..
Click to expand...
Click to collapse
Yup! After wanting to view my current steps for today, I just opened up Gliderun, waited a bit, and it connected to my MiBand after a couple of minutes. I have to close Gliderun in the meantime because my phone is relatively old (HTC One S -- 2, 3 years?) so I can't have the app running all the time.
About step count and the start button. Gliderun tries to combine activity and general tracking. When you start a particular activity (by clicking on start) it should count the steps of that activity. When you are not in a activity it should count those steps globally for a daily total.
Click to expand...
Click to collapse
Ohh, I see, that makes a lot of sense! I'm a student for the majority of my day and don't really have any separate 'activities', so I didn't see the inherent benefit of activity mode, but that does make sense.
To activate global tracking you can go to preferences > tracking or tap on some of the inactive dashboard indicators. Without global tracking activated you should still see some totals after syncronization with the band.
Click to expand...
Click to collapse
Ahh, I apologize about that, I completely neglected this tab. I figured the Activity tab was more important simply because of its location. This actually looks more like how I was hoping the app would function.
About sleep. The app should be already tracking your sleep periods. You can see those on Global stats screen. I would like to add the deep sleep phases but I need documentation or advise on what exactly I have to look for in order to provide a faithful solution.
Click to expand...
Click to collapse
Thank you! Again, if there are any logs I can provide that would help, please let me know and I will certainly do so.
--edit--
I'm having an issue where the app doesn't seem to be updating the Global Stats tab. On the Activity tab, my total steps have been counted properly, but when I go to Global Stats, it only shows information from the previous time I synced (about 8 hours ago). I killed the app, re-connected, and re-synced, and the same thing happened.
--edit #2--
After messing around with the Global Stats tab, and switching views (24 hours/day/week), the app resynced on its own (not sure if it was a coincidence or from me switching views), and now the Global Stats tab has updated; but now it has slightly more steps than the Activity tab.
Not a big deal at all, but I figured you'd like to know!
I just found your app. It looks very promising.
Where would you prefer to have me send the feedback.
I understood there was also a Reddit thread somewhere - I could not find it.
Thanks
maishsk said:
I just found your app. It looks very promising.
Where would you prefer to have me send the feedback.
I understood there was also a Reddit thread somewhere - I could not find it.
Thanks
Click to expand...
Click to collapse
If you want you can send me an email. If it something more general or open to discussion by other people feel free to post it here.
That Reddit thread is not getting any rythm.
I had a Mi Band and used the MiFit app for the last couple months, but I lost the device. I've ordered a new one and I'm going to start using Gliderun mostly because of the Google Fit integration. While I'm waiting for my package I've been messing around with your app and trying to figure some things out so I'll be ready to go when my new band arrives. Here's some feedback:
The headphone icon opens up the music controls and the audio notifications; music controls/library only works with music stored on the phone, is there any way to integrate this with Google Music? There's only a couple of apps that I've seen do this (specifically GMusicFS), but it would be nice.
On the user screen: for any user input requiring a number (weight, height, goals, etc.) you have a scrolling number which is nice from a UI perspective, but when I have to enter any of these values for the first time, scrolling is very tedious. This is particularly brutal when I'm trying to set up a goal for the first time, I have to scroll all the way from 0 to 8,000. There should be a way to manually input a number using an on-screen keyboard as well. It also looks like the goal is limited to 20,000 steps, theoretically this should be unlimited.
User profile: I have my units set to imperial. When inputting my height for the major intervals you might want to make the height max out at 7-ft just in case. For the minor intervals, you should put the unit next to the number (inches) and I would limit the user to discrete numbers 1 through 12. I'm not sure how you're calculating height, but the way you have it set up it is very hard for a user to input their height in imperial units. For example: I am 6-ft 2-inches, in order to input my height I have to calculate how many hundredths of a foot 2-inches is. So in my case 2/12=.16666. The average person isn't going to do this and is going to give up when you can't just enter 6-ft 2-inches.
The compass UI needs a little work, it isn't quickly evident where north is. I would prefer a more traditional looking compass (maybe something similar to this). Also, for some reason my altitude is always blank.
Synchronize: I have the first three options enabled for Google Fit integration. The app always says disconnected, when I press the synchronize button it changes to connected, but I don't think anything is actually being synced. There should be some sort of progress bar when synchronizing with Google Fit so the user knows it's actually working. In my case I don't think it's working at all. I've enabled the option to download tracked activities from GFit, but nothing ever shows up in the stats.
In the settings, General: I would make an expert section to the settings menu that has to be manually activated and move Optimize track points and Recalculate calories there. Also for any option where you could be deleting or modifying data (everything under the "Other" section) I would have a confirmation dialog box pop up. That way if somebody accidentally presses one of those options they don't completely wipe out all there data.
In the settings, Audio: I would either explain the difference between Audio engine A and B or give the user an option to play example audio. Similar to how you have the option to "Listen to an example" of text-to-speech output in the main android settings.
In the settings, Notification: I think there needs to be a little more configuration for notifications. I really like the way the Notification version of the MiFit app allowed you to set the colors for the LEDs on the Mi Band as well as the number of times it vibrated and the number of times the LED blinked. I know this is a beta version, but I think a little more work needs to be done in this particular area if you want users to switch from the MiFit app. Being able to tell what app I'm getting a notification from just by looking at the band is extremely useful and it's going to make switching hard without it. I don't want to say you should copy the Notification settings screen from the MiFit app, but it has been implemented very well.
Settings: somewhere you need to provide Help information. For most of the options I'm not sure exactly what they're supposed to do, maybe have a ?-button next to the option that the user can press that will pop up a longer description of exactly what the option does.
Any thoughts on providing a dark theme as well? Just something simple where you change the background to black and the text to white, the green color should look good with both a dark and light background.
I saw you have sleep tracking on the list of things to improve upon, really looking forward to that. The MiFit app and Sleep as Android app provide a very clean UI for visualizing your sleep. I would try to implement something similar. I'm sure you've seen it, but this thread might have some hints on how to better pull the sleep data from the MiBand.
I know I wrote a lot, but you have done great work with this app in the short amount of time you've been developing it. I can't wait to see how this app progresses because I think you've got a really good app here. The design looks very good and polished it just needs a few tweaks here and there. Once I get my new Mi Band I'll provide some more feedback.
Keep up the great work. If you want to discuss any of this more I would be more than happy to do so.
Thanks for all that feedback! I add everything to my list. Will tackle the more important stuff first.
About audio.
I may eventually add a fallback into system players. The player provides a rythm guidance for your exercise by adjusting the playback rate to your desired cadence so it is rather specific. it is custom built.
About scrolling. If you tap you do not need to scroll. You can enter the number directly. This is NumberPicker standard. I may have missed one or two fields though.
I will increase the daily goals to something in the ultramarathon range.
About imperial input. You are absolutely right. Will change it soon..
I will see what I can do with the compass. It is all a matter of priorities.
Altitude comes from GPS.
GFit issue is a glitch too. Click sync again. I'm now focusing more on FitnessSyncer as it is much more powerful.
Sleep tracking is working. You can see it on Daily Stats. It may need some tweaking though. The band does not really export sleep data so I had to write the algorithms myself and I've already noticed a couple of issues.
Also the custom notifications is a great idea. I have to fit that into a general API. The app is meant to integrate other bands. Just need to get some samples.
Devo7v said:
I had a Mi Band and used the MiFit app for the last couple months, but I lost the device. I've ordered a new one and I'm going to start using Gliderun mostly because of the Google Fit integration. While I'm waiting for my package I've been messing around with your app and trying to figure some things out so I'll be ready to go when my new band arrives. Here's some feedback:
The headphone icon opens up the music controls and the audio notifications; music controls/library only works with music stored on the phone, is there any way to integrate this with Google Music? There's only a couple of apps that I've seen do this (specifically GMusicFS), but it would be nice.
On the user screen: for any user input requiring a number (weight, height, goals, etc.) you have a scrolling number which is nice from a UI perspective, but when I have to enter any of these values for the first time, scrolling is very tedious. This is particularly brutal when I'm trying to set up a goal for the first time, I have to scroll all the way from 0 to 8,000. There should be a way to manually input a number using an on-screen keyboard as well. It also looks like the goal is limited to 20,000 steps, theoretically this should be unlimited.
User profile: I have my units set to imperial. When inputting my height for the major intervals you might want to make the height max out at 7-ft just in case. For the minor intervals, you should put the unit next to the number (inches) and I would limit the user to discrete numbers 1 through 12. I'm not sure how you're calculating height, but the way you have it set up it is very hard for a user to input their height in imperial units. For example: I am 6-ft 2-inches, in order to input my height I have to calculate how many hundredths of a foot 2-inches is. So in my case 2/12=.16666. The average person isn't going to do this and is going to give up when you can't just enter 6-ft 2-inches.
The compass UI needs a little work, it isn't quickly evident where north is. I would prefer a more traditional looking compass (maybe something similar to this). Also, for some reason my altitude is always blank.
Synchronize: I have the first three options enabled for Google Fit integration. The app always says disconnected, when I press the synchronize button it changes to connected, but I don't think anything is actually being synced. There should be some sort of progress bar when synchronizing with Google Fit so the user knows it's actually working. In my case I don't think it's working at all. I've enabled the option to download tracked activities from GFit, but nothing ever shows up in the stats.
In the settings, General: I would make an expert section to the settings menu that has to be manually activated and move Optimize track points and Recalculate calories there. Also for any option where you could be deleting or modifying data (everything under the "Other" section) I would have a confirmation dialog box pop up. That way if somebody accidentally presses one of those options they don't completely wipe out all there data.
In the settings, Audio: I would either explain the difference between Audio engine A and B or give the user an option to play example audio. Similar to how you have the option to "Listen to an example" of text-to-speech output in the main android settings.
In the settings, Notification: I think there needs to be a little more configuration for notifications. I really like the way the Notification version of the MiFit app allowed you to set the colors for the LEDs on the Mi Band as well as the number of times it vibrated and the number of times the LED blinked. I know this is a beta version, but I think a little more work needs to be done in this particular area if you want users to switch from the MiFit app. Being able to tell what app I'm getting a notification from just by looking at the band is extremely useful and it's going to make switching hard without it. I don't want to say you should copy the Notification settings screen from the MiFit app, but it has been implemented very well.
Settings: somewhere you need to provide Help information. For most of the options I'm not sure exactly what they're supposed to do, maybe have a ?-button next to the option that the user can press that will pop up a longer description of exactly what the option does.
Any thoughts on providing a dark theme as well? Just something simple where you change the background to black and the text to white, the green color should look good with both a dark and light background.
I saw you have sleep tracking on the list of things to improve upon, really looking forward to that. The MiFit app and Sleep as Android app provide a very clean UI for visualizing your sleep. I would try to implement something similar. I'm sure you've seen it, but this thread might have some hints on how to better pull the sleep data from the MiBand.
I know I wrote a lot, but you have done great work with this app in the short amount of time you've been developing it. I can't wait to see how this app progresses because I think you've got a really good app here. The design looks very good and polished it just needs a few tweaks here and there. Once I get my new Mi Band I'll provide some more feedback.
Keep up the great work. If you want to discuss any of this more I would be more than happy to do so.
Click to expand...
Click to collapse
Thanks for reading through my comments:
tincore said:
About audio.
I may eventually add a fallback into system players. The player provides a rythm guidance for your exercise by adjusting the playback rate to your desired cadence so it is rather specific. it is custom built.
Click to expand...
Click to collapse
The current implementation is good, it was more of a wish list item.
tincore said:
About scrolling. If you tap you do not need to scroll. You can enter the number directly. This is NumberPicker standard. I may have missed one or two fields though.
Click to expand...
Click to collapse
You're right I don't know how I missed that, apparently I've been using Android wrong this whole time.
tincore said:
I will increase the daily goals to something in the ultramarathon range.
Click to expand...
Click to collapse
I honestly would remove scrolling completely from the goals and just leave it as user input. I don't know if scrolling is very useful when we're talking about differences in thousands of steps.
tincore said:
About imperial input. You are absolutely right. Will change it soon..
Click to expand...
Click to collapse
Thanks
tincore said:
I will see what I can do with the compass. It is all a matter of priorities.
Click to expand...
Click to collapse
I don't see this as a priority, it was just a suggestion. Feel free to put this at the bottom of your list.
tincore said:
Altitude comes from GPS.
Click to expand...
Click to collapse
Apparently I was just in a bad location at the time. However it is reporting a different altitude than GPS Test. Gliderun shows me at an altitude of 119ft whereas GPS Test shows me at an altitude of 233 ft so I'm not sure what is going on. Is there some sort of log I can provide?
tincore said:
GFit issue is a glitch too. Click sync again. I'm now focusing more on FitnessSyncer as it is much more powerful.
Click to expand...
Click to collapse
I don't personally use FitnessSyncer, but I'm sure there are a lot of people who do. Looking forward to GFit integration. One quick question: once GFit is fully integrated, will I be able to sync all the data I collect with Gliderun or is there a limit on how far back I can go? Likewise will I be able to import all of my past GFit data into Gliderun?
tincore said:
Sleep tracking is working. You can see it on Daily Stats. It may need some tweaking though. The band does not really export sleep data so I had to write the algorithms myself and I've already noticed a couple of issues.
Click to expand...
Click to collapse
As I mentioned, I don't have my new Mi Band yet so I can't test sleep tracking yet. When I get it, I'll give you some more detailed thoughts on it.
tincore said:
Also the custom notifications is a great idea. I have to fit that into a general API. The app is meant to integrate other bands. Just need to get some samples.
Click to expand...
Click to collapse
The detailed control over notifications is the one thing I'm going to miss the most from the MiFit app. Hopefully it's not too much trouble to add these controls. The only thing I can think of to figure out how to add these controls would be to decompile the Notification version of the MiFit app or see if the api calls on this website are useful.
The more we talk and the more I mess around with the app the more I'm liking it.
Thanks again for all the valuable input!
Devo7v said:
Thanks for reading through my comments:
Click to expand...
Click to collapse
You are not the first one having trouble with the NumberPickers. I think they are not very well designed. I do not find the field edition intuitive either. Most of the time I forget to click accept so I lose the edition. Maybe I'm doing something wrong.
Devo7v said:
I honestly would remove scrolling completely from the goals and just leave it as user input. I don't know if scrolling is very useful when we're talking about differences in thousands of steps.
Click to expand...
Click to collapse
Yes. The plan is at least to space them in 100 or 250 units
Devo7v said:
Apparently I was just in a bad location at the time. However it is reporting a different altitude than GPS Test. Gliderun shows me at an altitude of 119ft whereas GPS Test shows me at an altitude of 233 ft so I'm not sure what is going on. Is there some sort of log I can provide?
Click to expand...
Click to collapse
At the moment I'm just showing the Altitude reported by GPS and I think that it has to be corrected by a complex calculation that can be retrieved from a webservice. That may be the issue.
Devo7v said:
I don't personally use FitnessSyncer, but I'm sure there are a lot of people who do. Looking forward to GFit integration. One quick question: once GFit is fully integrated, will I be able to sync all the data I collect with Gliderun or is there a limit on how far back I can go? Likewise will I be able to import all of my past GFit data into Gliderun?
Click to expand...
Click to collapse
Last time I tried it I could upload and download all gliderun data. I found GFit rather odd. Up to now it is unclear to me when it really uploads the data to the servers making it is visible from the web or other device. Also you do not retrieve exactly what you save.
Devo7v said:
As I mentioned, I don't have my new Mi Band yet so I can't test sleep tracking yet. When I get it, I'll give you some more detailed thoughts on it.
Click to expand...
Click to collapse
Sleep periods seem rather accurate. Still I have to do something to detect short sleep interruptions. Phases analysis is there too although I think that it has to be taken with a pich of salt. (Not only in this app)
Devo7v said:
The detailed control over notifications is the one thing I'm going to miss the most from the MiFit app. Hopefully it's not too much trouble to add these controls. The only thing I can think of to figure out how to add these controls would be to
Click to expand...
Click to collapse
It is no real trouble. I will add that rather soon (I hope)..
Hey Tincore
I think you have done some really great work on the app .. but when I tried to use it yesterday I got a bit confused (maybe you can help me out here).
I couldn't actually see where my step count was being shown. I was assuming it would be on the activity screen but it just didn't seem to update. Is there a way to force a refresh of the count? The only time the app seemed to update was when I reconnected my miband.
The update to fitnesssyncer worked well .. is there anyway to have it automatically sync (either time period or when you open the app possibly)?
I found a spelling mistake as well Where you add your weight and waist, chest, hip sizes there is a "thight" measurement (im guessing its meant to be thigh).
Thanks for your hard work!

[APP] Glimpse Notifications

~~~~~~ Introduction ~~~~~~
Using Android Lollipop/Marshmallow's lock screen notifications?
Tired of having to press the power button to see them?
Want your phone to turn on new notifications, but only when you grab to look at it?
Want your phone to turn on right when you take it out of your pocket?
Then this app is for you!
Introducing the all new efficiency app Glimpse Notifications:
{
"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"
}
​
This all new app fills an annoying hole in Android Lollipop's lock screen notification system. It's nice, it's shiny, but you always need to push that damn power button. This app does it for you, and also respects quiet times and whether or not your device is in your pocket.
It also does this:
recurring notifications (screen on and/or sound)
emulate LED notifications that the system lockscreen no longer shows
Double-tap to lock function for lockscreen
custom lockscreen display time
lockscreen lock-on-cover function
At the same time the app is completely for free and without ads!
~~~~~~ Downloads ~~~~~~
Google Play Store
Directly download APK
~~~~~~ FAQ ~~~~~~
FAQ (Google Doc)​
Looks interesting, thanks for sharing. I'm an ACDisplay user on an S4 but it doesn't seem to stay active the notification allowed so I'll try this.
thanks for this, it works well
only problem I found is that pocket detection doesn't work on my Samsung Galaxy S6
Bingley said:
Looks interesting, thanks for sharing. I'm an ACDisplay user on an S4 but it doesn't seem to stay active the notification allowed so I'll try this.
Click to expand...
Click to collapse
Yes, been using that one (and others) as well, but I always wondered why everybody wants to reinvent the lockscreen. I'm using a pattern lock and found none of the existing solutions to work well.
MJFox78 said:
thanks for this, it works well
only problem I found is that pocket detection doesn't work on my Samsung Galaxy S6
Click to expand...
Click to collapse
Strange. So, have you observed the screen turning on even if the proximity sensor is covered?
I plan on adding an extension to the pocket mode to cover the following use case: if the phone is pocketet or face down and you hear a notification, you typically take the phone and see what happened. Then I want it to turn on, but not necessarily everytime I take it out of my pocket. So something like "if coming out of pocket AND last notification less than N seconds ago -> turn on screen".
Perhaps we can sort your issues with the sensor out on the way.
xrad said:
Strange. So, have you observed the screen turning on even if the proximity sensor is covered?
Click to expand...
Click to collapse
yes, I covered the proximity sensor and sent the test notification and the screen turned on
I tried a different app that does basically the same like yours and it has the same problem, so maybe it's something related to Samsung?
xrad said:
I plan on adding an extension to the pocket mode to cover the following use case: if the phone is pocketet or face down and you hear a notification, you typically take the phone and see what happened. Then I want it to turn on, but not necessarily everytime I take it out of my pocket. So something like "if coming out of pocket AND last notification less than N seconds ago -> turn on screen".
Click to expand...
Click to collapse
sounds like a great feature! :good:
xrad said:
Perhaps we can sort your issues with the sensor out on the way.
Click to expand...
Click to collapse
let me know if you need me to test something!
keep up the good work! :highfive:
MJFox
Linked here from the OP's comment in the ACDisplay xda portal article. Looking very nice so far. Only feature I miss from ACDisplay is the active mode, i.e. screen on when removed from pocket, regardless of notification. This is a great way to keep power button use down, especially for devices like the N5 with known hardware button failures.
xrad said:
Yes, been using that one (and others) as well, but I always wondered why everybody wants to reinvent the lockscreen. I'm using a pattern lock and found none of the existing solutions to work well.
Strange. So, have you observed the screen turning on even if the proximity sensor is covered?
I plan on adding an extension to the pocket mode to cover the following use case: if the phone is pocketet or face down and you hear a notification, you typically take the phone and see what happened. Then I want it to turn on, but not necessarily everytime I take it out of my pocket. So something like "if coming out of pocket AND last notification less than N seconds ago -> turn on screen".
Perhaps we can sort your issues with the sensor out on the way.
Click to expand...
Click to collapse
+1 for this idea:thumbup:
Sent from my LG-D802 using XDA Free mobile app
el_smurfo said:
Linked here from the OP's comment in the ACDisplay xda portal article. Looking very nice so far. Only feature I miss from ACDisplay is the active mode, i.e. screen on when removed from pocket, regardless of notification. This is a great way to keep power button use down, especially for devices like the N5 with known hardware button failures.
Click to expand...
Click to collapse
Yeah I already assumed people will want that and I'm planning to cover this use case as well. Personally, when I had apps working like that in the past I found it a bit annoying that everytime I took out the phone to put it like on the table it turned on (even if there were pending notifications). That's why I thought about how I could narrow down the logic to be more useful.
xrad said:
Yeah I already assumed people will want that and I'm planning to cover this use case as well. Personally, when I had apps working like that in the past I found it a bit annoying that everytime I took out the phone to put it like on the table it turned on (even if there were pending notifications). That's why I thought about how I could narrow down the logic to be more useful.
Click to expand...
Click to collapse
Just make it a setting. Some people like it, some don't.
MJFox78 said:
yes, I covered the proximity sensor and sent the test notification and the screen turned on
I tried a different app that does basically the same like yours and it has the same problem, so maybe it's something related to Samsung?
Click to expand...
Click to collapse
A quick web search showed some reports that sounded a bit like what you're experiencing. So it could be a Samsung thing.
xrad said:
Download now and enoy:
Google Play Store​
Click to expand...
Click to collapse
Can you please provide the APK for those who doesn't have Play Store installed?
I would like to try your app on a Moto G 2013 running Cyanogenmod 12.1 (that doesn't have Ambient display enabled ).
Thanks in advance
-Sent from my Nokia 3320
Well, I have to say, this is a great app. The only thing it needs is the black list feature, that would really create a full circle of usability and applicability.
Keep up the great work..
nucleone said:
Well, I have to say, this is a great app. The only thing it needs is the black list feature, that would really create a full circle of usability and applicability.
Keep up the great work..
Click to expand...
Click to collapse
Thanks. Well, as a matter of fact I started out with having a black list and found that to be less useful than just marking the few notification sources I'm actually interested in (like Mail, SMS, WA). I'll think about throwing in a switch to configure black/white list behaviour, but it's not top of the list TBH.
MJFox78 said:
only problem I found is that pocket detection doesn't work on my Samsung Galaxy S6
Click to expand...
Click to collapse
Big oops here - I just realized that for the testing notification, I skip all the other checks because I figured it would confuse people if the other other filters prevented the test. Turns out the way I did it it confused us all. I'm going to change that in the next version (which is taking shape).
xrad said:
Big oops here - I just realized that for the testing notification, I skip all the other checks because I figured it would confuse people if the other other filters prevented the test. Turns out the way I did it it confused us all. I'm going to change that in the next version (which is taking shape).
Click to expand...
Click to collapse
I tried it out with a "real" notification (by sending myself an email)... still the screen turns on with the proximity sensor being covered
xrad said:
Thanks. Well, as a matter of fact I started out with having a black list and found that to be less useful than just marking the few notification sources I'm actually interested in (like Mail, SMS, WA). I'll think about throwing in a switch to configure black/white list behaviour, but it's not top of the list TBH.
Click to expand...
Click to collapse
Yeah, I can understand your point, but a black list, in addition to allowing users to block apps whose notifications they don't consider important/desirable, would also allow users to block out any app/process/service that Glimpse may report about, such as 'wireless networks available', you know, things from Android system or System UI, whose notifications just drain the battery without any real purpose.
But hey, it's just a suggestion, it's totally up to you what gets implemented.
Great app nevertheless..
Just pushed a new version: https://plus.google.com/105721704336323394016/posts/2rMtKQSLgu1
Let's see what Pandora's Box I have opened with the new Unpocket mode!
Enjoy!
moralesnery said:
Can you please provide the APK for those who doesn't have Play Store installed?
Click to expand...
Click to collapse
I added a download link in the OP.
Nice app...working great... ??
Could it be possible that instead of whole screen being lit up, only the area where notification is shown is lit up in black and white color? Just like active display ?
xrad said:
Just pushed a new version: https://plus.google.com/105721704336323394016/posts/2rMtKQSLgu1
Let's see what Pandora's Box I have opened with the new Unpocket mode!
Enjoy!
Click to expand...
Click to collapse
great work, pocket mode detection works now! :good:
the new unpocked mode is great as well, thanks a lot!
I just left a 5-stars review and some kind words in the app store, it's the least one can do!

[APP][4.1+] Powy - Use different shortcuts/Tasker Tasks through your power button

Powy
Powy gives you access to handy shortcuts through the power button. To trigger a shortcut you simply have to press the power button N times (you define how many times) and then the shortcut is triggered.
Powy provides the following shortcuts that you can use:
Hear the current time
Turn on or off your flashlight / torch / LED
Open camera app
Record audio
All of the shortcuts listed above work even if screen is off and/or device is locked. Does not have to be open or in recent apps to work.
You can enable only the shortcuts you want to be usable. You can configure shortcuts key combinations per shortcut. And you can start or stop Powy at any time.
Download
https://play.google.com/store/apps/details?id=com.danilomendes.powy
How to use?
Start Powy by pressing the button in the main screen of the app. Now to trigger the shortcut you want simply press the number of times configured in that shortcut (listed in the main screen).
Story behind Powy
Initially I've developed Powy only for my own needs, the initial purpose of Powy was to simply tell me the current time when I was using headphones, because I use headphones a lot and I'm kind of obsessed with time and I hated to have to take my phone out of my pocket to see what time it was. I developed a quick draft for myself and then now I figured that the app might be helpful to other people.
How it works - Technical description
Since we cannot actually listen to power button key events on background, Powy actually listens to screen on/off events and then after 0.714 seconds, after the last pressed key (maximum of 1.5 seconds), Powy sees if the total number of screen on and off's matches a shortcut and triggers it.
Permissions
RECEIVE_BOOT_COMPLETED - For the app to start running upon boot. This can be turned of whether or not you have Android 6+. You can turn it off on the Preferences section within the app.
CAMERA - *Only for Android versions below 6* This is simply used to use the flashlight.
WAKE_LOCK - Only used for the camera shortcut when it's triggered with the screen off. Powy does not keeps the wake lock for more than 100 ms after the camera shortcut is triggered.
FLASHLIGHT - For the flashlight.
RECORD_AUDIO - To record audio only when the record audio shortcut is triggered.
WRITE_EXTERNAL_STORAGE - Powy only uses this to write the recorded audio to the sdcard.
VIBRATE - Only to vibrate when record audio is triggered.
ACCESS_NETWORK_STATE & INTERNET - These two permissions are used by admob.
Try it and tell me what you think
I'm available to respond through this forum or through here.
Cumps,
Danilo Mendes
{
"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 would be really cool to hear some feedback from you guys on how to improve the app or if you are having difficulties using it. Thank you
danilo.mendes said:
It would be really cool to hear some feedback from you guys on how to improve the app or if you are having difficulties using it. Thank you
Click to expand...
Click to collapse
Whenever I try to get the >2 actions to run, I usually fail and it always just reads me the time. Maybe the 0.5s threshold is too low?
MishaalRahman said:
Whenever I try to get the >2 actions to run, I usually fail and it always just reads me the time. Maybe the 0.5s threshold is too low?
Click to expand...
Click to collapse
Hi thank you for replying.
I wrote the incorrect value, the threshold is actually 0.714 seconds. But in any case, try not to press the power button too quickly.
I think if it recognizes two screen on/off's it means it can capture more than that, meaning that the threshold is probably enough, but maybe the maximum time of 1.5 seconds it has to joins presses might not be sufficient.
But try not to press the power button too quickly and tell me how it goes.
Cumps,
Doesn't run on op3t.. freedom os7.1.1
The only one that works for me is "Tell me the time" on a Pixel XL running 7.1.1. I would totally donate if I could use this to toggle my flashlight.
earthplug said:
Doesn't run on op3t.. freedom os7.1.1
Click to expand...
Click to collapse
Hi,
I honestly haven't tested on freedomOS. Can you please give me more info on this? Does the app crashes? The shortcuts are not being triggered?
If the app does not crash try to press the power button calmly, because Powy actually depends on screen on/off events.
Keep me posted on this issue, thank you.
Cumps
overcoded said:
The only one that works for me is "Tell me the time" on a Pixel XL running 7.1.1. I would totally donate if I could use this to toggle my flashlight.
Click to expand...
Click to collapse
Hi, thank you for the feedback. Please note that Powy actually relies on screen on/off events. Try not to press the power button too quickly and confirm if the flashlight shortcut is ON (the switch is on).
Also, if you want, you can change the flashlight shortcut to 2 times power button . You just have to change the shortcut to '2 x Power button' simply by clicking on edit:
Cumps
It currently doesn't work for me on the LG G5 running Marshmallow. I tried using only the time function and pressing twice both quickly and slowly. Neither scenario triggers the action. This is a really cool idea and thanks for the app -- I hope I can get it working on my setup.
danilo.mendes said:
Hi,
I honestly haven't tested on freedomOS. Can you please give me more info on this? Does the app crashes? The shortcuts are not being triggered?
If the app does not crash try to press the power button calmly, because Powy actually depends on screen on/off events.
Keep me posted on this issue, thank you.
Cumps
Click to expand...
Click to collapse
The app doesn't load at all just flashes and that's it back to home screen.
Hi
Only flash shortcut works for me.
Salmusng S5 (neo), Android 6.01 stock.
However good app, thanks!
app crashes immedietly after introduction ends
my currents are in my signature
danilo.mendes said:
Hi, thank you for the feedback. Please note that Powy actually relies on screen on/off events. Try not to press the power button too quickly and confirm if the flashlight shortcut is ON (the switch is on).
Also, if you want, you can change the flashlight shortcut to 2 times power button . You just have to change the shortcut to '2 x Power button' simply by clicking on edit:
Cumps
Click to expand...
Click to collapse
Thanks for the reply, I have tried both slow and fast power button presses, as well as waiting for the screen to turn off before initiating more presses. Like I said, "say the time" does work, so I know what the timing is supposed to be like.
@danilo.mendes Cool idea bro..
I guess the reason why users are facing problems is that the time taken to receive consecutive SCREEN_ON/OFF broadcasts vary for different devices..
Instead of hardcoding the threshold value, you can get the data from user itself..
While opening the app for first time, you can ask the users to consecutively press the power button for N times for calibration purpose (N is your wish).
While the user is doing that, you may record (in your Service) the threshold timings between the SCREEN_ON/OFF broadcasts and compute the average for N trials.
And finally set that as threshold value.
That way, you may get the app working for all devices..
Hope my words are clear
GokulNC said:
@danilo.mendes Cool idea bro..
I guess the reason why users are facing problems is that the time taken to receive consecutive SCREEN_ON/OFF broadcasts vary for different devices..
Instead of hardcoding the threshold value, you can get the data from user itself..
While opening the app for first time, you can ask the users to consecutively press the power button for N times for calibration purpose (N is your wish).
While the user is doing that, you may record (in your Service) the threshold timings between the SCREEN_ON/OFF broadcasts and compute the average for N trials.
And finally set that as threshold value.
That way, you may get the app working for all devices..
Hope my words are clear
Click to expand...
Click to collapse
Hi, Yeah it seems like that's right. That's a really cool suggestion, thank you I'm going to use a mix of your suggestion, because I want to avoid complicating the setup for the first time users. So instead of asking the user, I'm thinking about calculating the threshold automatically for the first time then use those values by default. And also adding a preference for the user to configure the threshold and the max time.
I'll update the apk version asap with this changes. Again, thank you
Cumps
nhmanas said:
app crashes immedietly after introduction ends
my currents are in my signature
Click to expand...
Click to collapse
earthplug said:
The app doesn't load at all just flashes and that's it back to home screen.
Click to expand...
Click to collapse
Hi both, Thank you for the feedback. I just got a crash report related to the TTS (Text-To-Speech) and I'm going to fix it and include it in the next client that I'll upload very soon.
Cumps
sugerdroid said:
It currently doesn't work for me on the LG G5 running Marshmallow. I tried using only the time function and pressing twice both quickly and slowly. Neither scenario triggers the action. This is a really cool idea and thanks for the app -- I hope I can get it working on my setup.
Click to expand...
Click to collapse
Publiuss said:
Hi
Only flash shortcut works for me.
Salmusng S5 (neo), Android 6.01 stock.
However good app, thanks!
Click to expand...
Click to collapse
Hi both, Thank you for the feedback Like GokulNC said, some devices seem to have more different times of screen off/on events than I expected. For this reason I'll develop some changes to make this more flexible and hopefully this will fix your issues. This will be in the next release that I'll release very soon.
Cumps
GokulNC said:
@danilo.mendes Cool idea bro..
I guess the reason why users are facing problems is that the time taken to receive consecutive SCREEN_ON/OFF broadcasts vary for different devices..
Instead of hardcoding the threshold value, you can get the data from user itself..
While opening the app for first time, you can ask the users to consecutively press the power button for N times for calibration purpose (N is your wish).
While the user is doing that, you may record (in your Service) the threshold timings between the SCREEN_ON/OFF broadcasts and compute the average for N trials.
And finally set that as threshold value.
That way, you may get the app working for all devices..
Hope my words are clear
Click to expand...
Click to collapse
overcoded said:
Thanks for the reply, I have tried both slow and fast power button presses, as well as waiting for the screen to turn off before initiating more presses. Like I said, "say the time" does work, so I know what the timing is supposed to be like.
Click to expand...
Click to collapse
nhmanas said:
app crashes immedietly after introduction ends
my currents are in my signature
Click to expand...
Click to collapse
Publiuss said:
Hi
Only flash shortcut works for me.
Salmusng S5 (neo), Android 6.01 stock.
However good app, thanks!
Click to expand...
Click to collapse
earthplug said:
Doesn't run on op3t.. freedom os7.1.1
Click to expand...
Click to collapse
overcoded said:
The only one that works for me is "Tell me the time" on a Pixel XL running 7.1.1. I would totally donate if I could use this to toggle my flashlight.
Click to expand...
Click to collapse
sugerdroid said:
It currently doesn't work for me on the LG G5 running Marshmallow. I tried using only the time function and pressing twice both quickly and slowly. Neither scenario triggers the action. This is a really cool idea and thanks for the app -- I hope I can get it working on my setup.
Click to expand...
Click to collapse
Hi everyone,
Powy 1.0.2 released
Added:
Now the threshold and max time of key presses and shortcuts are configurable
Fixed crash caused by no TTS engine in some ROMs (e.g.: LG G5)
Added method to automatically find best threshold and max time when you use the first shortcut (only on clean installs)
Get it at: https://play.google.com/store/apps/details?id=com.danilomendes.powy
So now, hopefully, all issues should be resolved and the app becomes more flexible because you can configure the settings for each device and to your needs.
Tell me what you think about this new release and rate as you think it's fit
Thank you all for the feedback it was really helpful.
Cumps
Took a little playing with it, but the flashlight is now working for me, thanks!
overcoded said:
Took a little playing with it, but the flashlight is now working for me, thanks!
Click to expand...
Click to collapse
That's good to hear
Thanks for replying back
Hi guys,
Just wanted you to know that Powy now allows you to use Tasker Tasks through the power button. This is now available on version 1.1.0. I think that now by using Powy combined with Tasker you have a lot of flexibility customizing shortcuts on your power button.
For example, now you can add a task on Tasker that turns WiFi on/off and then fire it using your power button through Powy.
Give it a try and tell me what you think
Powy: https://play.google.com/store/apps/details?id=com.danilomendes.powy
Tasker: https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm

[APP] 10th Aug. ◦ Edge Sense Plus 1.8.0 ◦ Customize Active Edge on your Pixel 2

{
"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"
}
Featured by:
XDA-Developers: Customize the Google Pixel 2’s Active Edge to do any action with Edge Sense Plus [XDA Spotlight]​
What is Edge Sense Plus?
Edge Sense Plus was initially just meant for the HTC U series. It let's you customize the squeeze action and adds some more squeeze gestures and features.
But with the Pixel2 also coming with a squeezable frame I had the goal to make it compatible with it too.
..and after a couple of days debugging with @k4r70ng (I don't own the device, big thanks to him, was a great help) we are here now!
Requirements
You have to be on Oreo 8.1 or Android P.
You need to run a STOCK based ROM, because Active Edge is broken on AOSP roms.
You need to be rooted with magisk to use it.
Install the Active Edge System Mod Magisk Module from the MagiskManager Repo and the EdgeSensePlus from the playstore and you are ready to go!
Telegram Group
Join Telegram Edge Sense Plus Group
How does it work
To make it working on the Pixel2 I had to modify the SystemUIGoogle.apk that runs the ElmyraService (Service that processes the squeeze gestures).
I intercept the events and pass them to the EdgeSensePlus Application that starts the appropriate action then that you selected.
Some more adjustments were made, so the squeezing also works when you are in immersive mode, camera or when Google Assistant is deactivated/uninstalled.
What can it do?
Custom actions:
Currently you can choose from over different actions
Quickly Start camera - Also when screen is off and locked
Per App Action - Execute different squeeze actions depending in what app you are!
Sidebar
Gesture Panel - Draw custom gestures to start different actions
Custom App
Shortcuts - e.g. to make direct calls, start tasker tasks and more!
Scroll up/down
Flashlight
Recent Apps
Toggle Autorotation
Autobrightness (6 states: Auto, Min, Low, Mid, High, Max)
Split Screen
Expand/Collapse Statusbar
Toggle NFC
Toggle Display on/off
Toggle Autorotation
Toggle DND
Toggle Vibration
Toggle Bluetooth
Toggle WiFi
Music Play/Pause
Previous Track
Next Track
Toggle Keep awake
Google Assistent
Lock Screen
Back
Home
Toggle Sync
Sync all accounts
Previous App
Take Screenshot
Clear all notifications
GPS
Answer/End call
Immersive Mode
Shell command
Per app actions:
With the per app action, you can define different squeeze actions per app. So the chosen action will be executed dependent in what app you are currently are.
Double Squeeze: (Premium)
If you often accidentally trigger a short squeeze, that won't happen anymore if you map your desired action to the double squeeze gesture.
You can define a double squeeze interval, to ensure you are quick enough to trigger it every time.
Long Squeeze:
Missed a long squeeze action on your Pixel? Edge Sense Plus has it!
G-Sensor usage: (Premium)
If enabled, will be able to execute different actions depending on the current position of your device, whether it is flat or upright in your hand.
That way you can have six different squeeze gestures: short, long, doublepress in flat or upright device position.
Media control:
The media control will override your set squeeze actions while media is playing so you can control your media.
That includes play/pause, increase/decrease volume and skip to next and previous track.
Squeeze sounds:
Ever thought it would be funny if a squeeze of your Pixel2 would make a sound, if it is a *click*, *oink* , *fart* or whatever you think of?
You can use any .mp3 file to make that happen!
Sidebar:
The Sidebar has 4 different panels, Applications, Shortcuts, Recent Apps (Premium), Quicksettings (Premium).
Panel colors are customizable
Instructions
You must be on at least Oreo 8.1 to to be able to use it. Root with Magisk is required since the magisk module is mandatory!
It is recommended to have a working TWRP backup in case something goes wrong. Check the FAQ for help too.
Like always: Flash on your own risk. I'm not responsible for any damaga to your device
Flash the Magisk Module either in Magisk Manager or TWRP
Install Edge Sense Plus
Enjoy.
Downloads
Now also available via the MagiskManager Repo:
I recommend to install and update the Magisk Module directly via the MagiskManager repository directly in the MagiskManager app.
All releases will be also available on the GitHub repository
Edge Sense Plus:
Ok lol I am blind, thanks for app!
This looks great and more powerful than other options to intercept the squeeze gesture. Thanks for taking the time to port it!
Would it be possible to provide a module download with an Md5? I downloaded and flashed the module, wound up in a bootloop and had to restore a backup. I'd like to try this, but really want to be careful. Thanks
FAQ
Q: Will it also work on the Pixel2 XL?
A: No, it will bootloop your device. There is a separate thread on the Pixel2 XL forum.
Q: My device bootloops after flashing the magisk module.
A: Ensure you are on the latest Pixel2 OTA. To get out of the bootloop, go to the magisk thread and install the magisk uninstaller and then reinstall magisk again.
Q: The magisk module zip is greyed out when I try to install it.
A: I have no explanation why it happens for some. Install a FileManager like SolidExplorer or FX File Explorer, then Select that File Browser in the System File Explorer to select the path
Thanks. Yeah Pixel 2 on the latest January update with TWRP and Magisk 15.2.
Yep it was a bad download. Thanks for the Md5. I'm all set now :good:
jascolli said:
Yep it was a bad download. Thanks for the Md5. I'm all set now :good:
Click to expand...
Click to collapse
great, glad to hear.
Love the app so far! One thing that bothers me is that when I launch google assistant, it makes the beeping noise twice. Is there anyway to change that?
SuperSmashedBro said:
Love the app so far! One thing that bothers me is that when I launch google assistant, it makes the beeping noise twice. Is there anyway to change that?
Click to expand...
Click to collapse
Aware of that. Will look into this today. Does not happen on my U11... so debugging will take a bit longer.
Are there any plans to distribute the app through the Play Store? And is it normal for the app to constantly ask me to upgrade to premium? By constantly, I literally mean constantly. It seems to be tied to scrolling down the settings page, and it pops up 2-3 times before I reach the bottom.
Also, will squeezing still silence an incoming call? Are there any settings that might prevent the squeeze from silencing an incoming call?
AZImmortal said:
Are there any plans to distribute the app through the Play Store? And is it normal for the app to constantly ask me to upgrade to premium? By constantly, I literally mean constantly. It seems to be tied to scrolling down the settings page, and it pops up 2-3 times before I reach the bottom.
Also, will squeezing still silence an incoming call? Are there any settings that might prevent the squeeze from silencing an incoming call?
Click to expand...
Click to collapse
Currently the app is just visibible for HTC U Devices.
Im afraid of bad ratings from pixel users, since it does just work with root. On the U11 it works without.
Will try improve the scrolling issue.
I just override the google assistant action. So the other native squeeze actions should still work.
AZImmortal said:
Are there any plans to distribute the app through the Play Store? And is it normal for the app to constantly ask me to upgrade to premium? By constantly, I literally mean constantly. It seems to be tied to scrolling down the settings page, and it pops up 2-3 times before I reach the bottom.
Also, will squeezing still silence an incoming call? Are there any settings that might prevent the squeeze from silencing an incoming call?
Click to expand...
Click to collapse
Can you check if that fixes the scrolling issue?
https://www.dropbox.com/s/1rs8vn24o27vrxb/app-release.apk?dl=0
j to the 4n said:
Can you check if that fixes the scrolling issue?
https://www.dropbox.com/s/1rs8vn24o27vrxb/app-release.apk?dl=0
Click to expand...
Click to collapse
Your update seems to have fixed the constant update pop-up for me. Thanks! Just bought pro for the additional features. Awesome work!
Sent from my Pixel 2 using Tapatalk
btreu1 said:
Your update seems to have fixed the constant update pop-up for me. Thanks! Just bought pro for the additional features. Awesome work!
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Much appreciated (-:
I've noticed that pocket detection makes active edge misbehave. I don't know if this is a known issue, but I thought I'd share my experience.
The other thing I thought was an issue was with setting a shortcut to a Tasker task. For anyone who may not understand how it works, you have to open Tasker and choose "exit" from the menu at the top right of the app before you can set the task shortcut in Edge Sense Plus.
Sent from my Pixel 2 using Tapatalk
btreu1 said:
I've noticed that pocket detection makes active edge misbehave. I don't know if this is a known issue, but I thought I'd share my experience.
The other thing I thought was an issue was with setting a shortcut to a Tasker task. For anyone who may not understand how it works, you have to open Tasker and choose "exit" from the menu at the top right of the app before you can set the task shortcut in Edge Sense Plus.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
In what way misbehave? No issues reported yet on the u11 for half a year
Playstore compatibility for Pixel2/XL
burp

Categories

Resources