~~~~~~ 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!
Related
Void Lock
A Secure and Convenient Gesture Lockscreen
Features:
-Gesture Unlock
-Key Combo Unlock
-Gesture to launch apps from lockscreen
-Gesture to change settings like Vibrate and WiFi from lockscreen
-MugShot
-And... anything else you can just read from the description on the Market Page.
Pics:
{
"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"
}
Issues:
Make sure to follow every instruction when doing the Setup. Especially on the brightness part.
Update:
1.9
-Lots of bugfixes. Improved launching and also removed screen flickering
-Attempt to get rid of navigation bar for ICS devices that has no hard keys
-Added in Setup Brightness to Settings. Added in new gestures: Show Notifications and Glimpse Text.
1.8
-ICS Support
-Able to set Void Lock as default Home Launcher now for more security and bugfixes
-Fix for status bar showing, only if set as default Home Launcher.
-Fix for popups showing up that blocks gesture and keys input.
1.6
-Fixed MugShot crashes
-Added requested feature: Shortcut to toggle on/off status of Void Lock.
1.5
-Fixed stock lockscreen bug
1.4
-New Setup Screen!
-New attempt at fixing bug with stock lockscreen
-Added 5 tips
1.3
-Added setting for SoftKey Lights Off. Find in Essentials.
-Added setting for custom brightness for settings like Show Time. Find in Essentials.
-Added Notification to prevent system from closing service. Able to lock from Notification.
-Added Information Section in Settings. Information section contains Uninstall Info, Tips, and EmailMe.
1.25
-Fixed up a bug related to calling. Lockscreen should not interfere with any Incoming and Outgoing calls anymore.
-Fixed up Setup bug. All devices should be able to finish Setup now.
-Turned off Start at Boot by default. New users can now reboot to remove lockscreen if there are any problems. When the lockscreen can be unlocked properly, go to Essentials in Settings to turn on Start at Boot.
1.2
-Fixed up the lockscreen interference with Calling.
-Modified order of launching. Should stop the stock lockscreen from showing up now. At least it does for my devices. If any devices still has the stock lockscreen showing, tell me which device it is.
-New Feature: Screen Timeout replacement. When screen timeout activates, it will launch Void Lock instead of turning off the screen. Enable it in Experimental Section of Settings.
Links:
Free Version
Nice app, need translation?!
Nice app.
I found the setup a bit confusing, but i don't really know how it could be made better.
After trying it i got some FCs:
I was using the unlock feature.
http://pastie.org/3074624
http://www.pastie.org/3074625
I'm using a i9000 on latest cyanogen build from repo.
I would make screenshots with another font ;-).
djkidy123 said:
Nice app, need translation?!
Click to expand...
Click to collapse
thanks, translations are always welcome.
Dark3n said:
Nice app.
I found the setup a bit confusing, but i don't really know how it could be made better.
After trying it i got some FCs:
I was using the unlock feature.
http://pastie.org/3074624
http://www.pastie.org/3074625
I'm using a i9000 on latest cyanogen build from repo.
I would make screenshots with another font ;-).
Click to expand...
Click to collapse
Yea, I wasn't too happy with the setup, but... I only found out about the brightness thing after testing it out on a i9000 too. Tried a more automated approach, but doesn't produce the same results as regular presses. I'll upgrade the setup process when I find a better solution.
Thanks for the logs, I tried reproducing the problem, but didn't get a force close, but I think I might know what the problem might be.
Will get to work on that.
lol the font looks really really cute.
I'm still not able to reproduce the forceclose, but thanks to the logs, I believe I fixed the problem. One of them was leftover code I missed removing which strangely wasn't causing me any problems.
The other... should be fixed.
You'll see an update soon.
doesn't work on ICS 4.0.2...
matiu said:
doesn't work on ICS 4.0.2...
Click to expand...
Click to collapse
I confess, I have not been able to test it out on ICS yet...
Which phone are you using and which part doesn't work?
New update! Should fix up the phones having the lockscreen suddenly locking and also those who still has their stock lockscreen show up.
Sent from my LG-P920 using XDA App
constant FC on the setup wizard (when setting unlock key)
nexus s 4.0.3
if you need help testing on ICS i can help you with beta-test. PM me if you'd like that.
DevJackey said:
I confess, I have not been able to test it out on ICS yet...
Which phone are you using and which part doesn't work?
Click to expand...
Click to collapse
Google Galaxy Nexus, your application crash during the setup (after making the first gesture)
matiu said:
Google Galaxy Nexus, your application crash during the setup (after making the first gesture)
Click to expand...
Click to collapse
Thanks I'll investigate.
Sent from my LG-P920 using XDA App
Had to use No Lock app, to disable normal lock screen, then set the VOID, work great!
Nice work there....but i have one problem tough....during calls the phone gets locked itself and i have to unlock it again to hang up and stuff
And could you add a "disable stock lockscreen" feature?? It would be highly appreciated
csoulr666 said:
Nice work there....but i have one problem tough....during calls the phone gets locked itself and i have to unlock it again to hang up and stuff
And could you add a "disable stock lockscreen" feature?? It would be highly appreciated
Click to expand...
Click to collapse
I'm currently fixing up the call lock right now.
There wasn't a disable stock lockscreen feature because it was supposed to disable the stock lockscreen automatically. However, that only seems to be working on the phones I'm testing on and strangely, the phones I can test on won't show the stock lockscreen, but some others does.
I'll be doing some more work into this part.
Update
New update out. Fixed up the calling. Now, the incoming call and incall screens won't be locked up. After call, it will lock back up. This works if you press the power button to turn off too.
New Feature. Find it in experimental setting. New feature affects the screen time out. Now, if you want, the Screen Timeout will lock with Void Lock instead of turning off the screen. Good feature for those like me who uses the WakeLock and avoids using the power button.
I forgot to disable my other lock screen and now seem to be locked out of my phone. Evo 4g with decks rom. any suggestions?
Great dev! can't wait for it to work completely on ICS
Couple of issues
evo 3d: when going to uninstall the uninstall screen flashes like crazy, buttons are highlighted (force stop, clear data, move to sd, uninstall) and blinking, takes several taps before you can get it uninstalled.
evo 4g: also when uninstalling it flashes, sometimes you have to clear data, move to SD card, then uninstall
it's one of the oddest things I've ever seen... and no, I'm not the one who left the nasty market comments.
18rmiller said:
I forgot to disable my other lock screen and now seem to be locked out of my phone. Evo 4g with decks rom. any suggestions?
Click to expand...
Click to collapse
I believe you have emailed me about this problem. I've replied to the email.
roshga said:
Great dev! can't wait for it to work completely on ICS
Click to expand...
Click to collapse
Thanks, I also can't wait for it.
mildlydisturbed said:
Couple of issues
evo 3d: when going to uninstall the uninstall screen flashes like crazy, buttons are highlighted (force stop, clear data, move to sd, uninstall) and blinking, takes several taps before you can get it uninstalled.
evo 4g: also when uninstalling it flashes, sometimes you have to clear data, move to SD card, then uninstall
it's one of the oddest things I've ever seen... and no, I'm not the one who left the nasty market comments.
Click to expand...
Click to collapse
Wow! that's also one of the oddest things I've heard about.
But, I can't imagine why it would happen. None of my code goes beyond the lockscreen and shouldn't affect the uninstalling at all. I just did an uninstall on my phone, tablet, and old phones to see if I get the same issue, but it was able to be uninstalled properly.
The only uninstall issue I know of is that the app is granted Device Admin status after the first time you press the Void Lock app, but that will only give you an Uninstall is not Successful message instead of the issues you are having.
Also odd that it happened to both of your phones.
I can't seem to think of why that uninstalling problem happened and I'm 100% positive that none of the code for Void Lock will affect the uninstalling. But if all that flashing and etc happens only when you are uninstalling Void Lock then Void Lock should definitely be the culprit. Its so strange...
Hmm, could it be related to your rom?
I also never had to clear data or move to SD card to uninstall it. Just disable device admin in the phone's Security Settings and then uninstall it and it'll work properly.
I'm not too worried about the market comments. I guess I expect it because of all the incompatibility issues I have not been able to predict when I released it. Yet, it does work for a lot of phones so I wouldn't even know which phones to restrict. All the problems seems to be coming from manufacturers making changes to the default lockscreen. Still working on fixing all of that right now.
I am a bit upset at those nasty market comments that rates low because of not being able to uninstall. I did give instructions in the market description. I guess I'll need add a new tab in the Settings to describe how to uninstall.
nice lockscreen.
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
Hey guys.
Stumbled upon this on YouTube. Bought the app and I can confirm that it works.
This is the app: https://play.google.com/store/apps/details?id=com.used.aoe
Here's the video I found on YouTube:
I managed to get it setup just the way I like. The guy in the video is a bit hard to understand but the video is good enough to get you started.
If your looking for a deeper dive into the optimal configuration process try this thread
https://forum.xda-developers.com/s10-plus/how-to/workaround-missing-notification-led-edge-t3919286
Enjoy!
thanks a lot =)
But is it posible to set different colors for different apps?
for example
green = whatsapp
blue = facebook ....
UPDATE: there is an option .... "when a notification comes" there you got the option "select enabled aps ots color and time" the blue button =)
neigo said:
thanks a lot =)
But is it posible to set different colors for different apps?
for example
green = whatsapp
blue = facebook ....
Click to expand...
Click to collapse
Yes
Thanks for the effort.
Just tried it, buggy as hell and didn't play nice with my lock screen. Also every 30 seconds the screen would flicker.
I'll keep an eye on it and maybe try again after more refinement.
bomp306 said:
Just tried it, buggy as hell and didn't play nice with my lock screen. Also every 30 seconds the screen would flicker.
I'll keep an eye on it and maybe try again after more refinement.
Click to expand...
Click to collapse
I had nothing but issues out of the app. Notifications wouldn't notify, the lock screen turned on and off randomly, there were no edge lighting effects no matter what I adjusted. I even tried to use the camera cutout, it again did not work.
This is a VERY bloated app, containing a LOT of features and options that frankly, are of no use to me or of no interest to me. I want an app that it's ONLY purpose is to alert me when I get messages, calls, and email. one that does not have so much bloat so that the developer can focus on the feature that is most sought after at the moment.
Just my two cents.
tl;dr App is junk, has too much junk, we need a debloated app.
It's a start...
b3y0ndd34th said:
I had nothing but issues out of the app. Notifications wouldn't notify, the lock screen turned on and off randomly, there were no edge lighting effects no matter what I adjusted. I even tried to use the camera cutout, it again did not work.
This is a VERY bloated app, containing a LOT of features and options that frankly, are of no use to me or of no interest to me. I want an app that it's ONLY purpose is to alert me when I get messages, calls, and email. one that does not have so much bloat so that the developer can focus on the feature that is most sought after at the moment.
Just my two cents.
tl;dr App is junk, has too much junk, we need a debloated app.
Click to expand...
Click to collapse
Come on! This app might not be right for you, but the developer should at least be given some credit/thanks for the effort taken to solve a problem, for which several users are seeking a not really forthcoming solution from Samsung. You "want an app...", but the developer created something and shared it. Granted, the app has far too many options and choices, but I was able to get it working to my satisfaction. Let's be thankful first .
- Paul
cmexec said:
Come on! This app might not be right for you, but the developer should at least be given some credit/thanks for the effort taken to solve a problem, for which several users are seeking a not really forthcoming solution from Samsung. You "want an app...", but the developer created something and shared it. Granted, the app has far too many options and choices, but I was able to get it working to my satisfaction. Let's be thankful first .
- Paul
Click to expand...
Click to collapse
Okay, okay, okay. I may have been a little harsh. I didn't mean to demean to developer. I am very thankful they have taken the time to create this app out of the kindness of their heart, as well as make the app free. I appreciate the work they have done and I would even donate if I could get the app to work; however it's not very user friendly tough, and in my opinion, could use a lot of work on many different aspects.
My main issue with the app is that it does not work as intended. I have tried using the youtube video settings, playing with options, etc.
I download and re-install this app about 5 times a day in hopes that MAYBE one time I can get it to function as intended. But I do not get any kind of Edge lighting or Notch cutout alert when I get messages, and that is the sole purpose of my attempts with this app, if I could find something similar or something that better served this purpose I would use it instead.
Sometimes, while using the apps lock screen, it will display the little icon and the message but then it goes away, and doesn't re-alert like it is suppose to, and the light affects do not appear. I have tried leaving it as the stock color and using a custom color. I have tried using the app lock screen, I have tried using the settings within the app to let it manipulate the wallpaper and lock screen, tried it with an image and also just a black background. I never even delved into setting different colors for apps, I can't get the dang notifications to work!
end rant
Do you have edge light on? Worked for me first try. I am not saying its 100% but for free and for now to wait to see if Samsung might give us we want I will leave it on my phone.
hello,
with this app is there a setup to leave the screen off when a notification comes in and only the cam ring turns on then?
thanks
m8980 said:
hello,
with this app is there a setup to leave the screen off when a notification comes in and only the cam ring turns on then?
thanks
Click to expand...
Click to collapse
Yes
it is working a bit strange for me as well. I've managed to get it to ALMOST work how I want, but I can't figure out why it will do random things
-- for a while it was turning on my screen when the edge lighting came on, which was pointless. I changed a lot of settings in troubleshooting, but I'm not sure what I did to fix it
-- also, it does notify every 30 seconds even though I have no new notifications. that one I haven't figured out yet
It does work as advertised though, despite the bugs I can't fix. It will either light up my edge lighting or the notch around the camera (which I prefer). so props to the dev for figuring that part out and here's to hoping the rest of the bugs get worked on the S10 (and my S10+). it seems to be working for other devices (I originally found it here for the oneplus)
dragonOL2 said:
it is working a bit strange for me as well. I've managed to get it to ALMOST work how I want, but I can't figure out why it will do random things
-- for a while it was turning on my screen when the edge lighting came on, which was pointless. I changed a lot of settings in troubleshooting, but I'm not sure what I did to fix it
-- also, it does notify every 30 seconds even though I have no new notifications. that one I haven't figured out yet
It does work as advertised though, despite the bugs I can't fix. It will either light up my edge lighting or the notch around the camera (which I prefer). so props to the dev for figuring that part out and here's to hoping the rest of the bugs get worked on the S10 (and my S10+). it seems to be working for other devices (I originally found it here for the oneplus)
Click to expand...
Click to collapse
you need to disable edge lighting in setting to use this app or else it will conflict since this app does wake up the screen while edge lighting is not.
if u enable both that mean this app waking up the screen, then edge lighting will also showing (coz edge lighting while screen is on is applied). you will have both notification then
psy07 said:
you need to disable edge lighting in setting to use this app or else it will conflict since this app does wake up the screen while edge lighting is not.
if u enable both that mean this app waking up the screen, then edge lighting will also showing (coz edge lighting while screen is on is applied). you will have both notification then
Click to expand...
Click to collapse
thanks! Not sure if it was changing that setting that helped, or their recent update I got yesterday, but the weird behavior has seemed to subside for a bit... I'll give it a few more days of testing to see if I can find anything else weird, but so far so good. I might also try swapping out the default color with individual colors for each app soon. Glad the dev seems to be open and receptive to feedback and willing to keep his app updated to fix various bugs found
The Reminder Notification Option
Has anyone successfully gotten the reminder option to work? When used, this is supposed to repeat the notification lighting for a brief period, if a notification had been unanswered for a period of time (30 or 60 seconds - I think). However, I could not get that to work - or at least replay the lighting. incidentally, I notice that Sakitech did not "fully" demo this feature in his Youtube tutorial. He mentioned it (at about 6:08), but did not show it working, I suspect (only speculating...) that he edited it out of the video because it does not work properly.
If anyone has the right settings for **** please share.
DetoxVenom said:
If anyone has the right settings for **** please share.
Click to expand...
Click to collapse
Did you whatch the video in the OP? It's sorta thorough.
Sent from my SM-G975W using XDA Labs
View attachment 4734017
cmexec said:
Has anyone successfully gotten the reminder option to work? When used, this is supposed to repeat the notification lighting for a brief period, if a notification had been unanswered for a period of time (30 or 60 seconds - I think). However, I could not get that to work - or at least replay the lighting. incidentally, I notice that Sakitech did not "fully" demo this feature in his Youtube tutorial. He mentioned it (at about 6:08), but did not show it working, I suspect (only speculating...) that he edited it out of the video because it does not work properly.
Click to expand...
Click to collapse
Use these settings and save.
rogerandgina said:
View attachment 4734017
Use these settings and save.
Click to expand...
Click to collapse
Thanks! The only setting I have differently is "double top to close" instead of "swipe up to close". Otherwise, I have been using these exact settings . As usual, at the moment that the screen should display the reminder, all that happens is the phone vibrates, but the light is not illuminated or display any visible interaction with the AOE lighting app.
cmexec said:
Thanks! The only setting I have differently is "double top to close" instead of "swipe up to close". Otherwise, I have been using these exact settings . As usual, at the moment that the screen should display the reminder, all that happens is the phone vibrates, but the light is not illuminated or display any visible interaction with the AOE lighting app.
Click to expand...
Click to collapse
Yeah, I see what you mean. My app as well will not work properly. I don't know what is going on? I have reached out to the developer and still not able to resolve the issues. The app starts out good but then goes rogue after awhile. I thought it was good lock messing it up but I was wrong. I give up for now.
cmexec said:
Thanks! The only setting I have differently is "double top to close" instead of "swipe up to close". Otherwise, I have been using these exact settings . As usual, at the moment that the screen should display the reminder, all that happens is the phone vibrates, but the light is not illuminated or display any visible interaction with the AOE lighting app.
Click to expand...
Click to collapse
Try turning off the "Manually only when I want it, I open the app". Also change the "When a notification comes" "And screen is off" to "Always off or on". Be sure you have turned off the Edge lighting in your phone settings.
What I was finding is when a notification would come in, it would light up the screen for a second and this would cause the app not to show the notification because I set it to "And screen is off" condition causing several notifications, if not all, to make the app not work. Once I changed to it to either/or, it has been working great for me. Hope this helps
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
Hello everyone!
I'm using the Samsung Galaxy Watch 4 with a Pixel 3a XL and I was a bit annoyed that the option to synchronize the Do Not Disturb (DND) state between watch and phone seems to be only available when paired to a Samsung phone. So I made an App to fix this and I'd like to share it with as many people as possible (I don't know how much interest there is).
{
"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"
}
As for now it is not in the Google Play Store but you can find the APK files, instructions and the source code on my GitHub.
Besides the DND sync I also implemented to (optionally) toggle Bedtime mode on the watch depending on the DND state of the phone (this is a bit experimental though, since I had to use an Accessibility Service for that, more on that below).
NOTE: For bedtime mode toggle to work it is important that the Bedtime Mode button is on the first page of quick settings and in the first row the button in the middle!
The installation on the watch is a bit technical (needs ADB) and here I want to explain why it is how it is.
Why do I need ADB?In order to listen to DND changes and also change the DND state, the app needs the permission from the user. On the phone it is no problem to grant said permission (it's the ACCESS_NOTIFICATION_POLICY for those curious) because the system provides a permission screen where the user can handle that permission. On the watch this screen is missing and therefore the user can't grant the permission to the watch. That's where ADB comes into play. I found a command which allows to enable the permission for the app via ADB. (I could only test this with my watch, I think (and hope) it will work on other devices too) In order for the app to work properly, you have to execute this command once after installation. The details are in the GitHub instructions.
Why is Bedtime mode experimental?In an ideal world I would know a command to use in my program that controls the Bedtime mode setting directly. Unfortunately I haven't found such a command (if anyone knows, please let me know). As a workaround I figured I could simulate the touch gestures which you would use to do it manually: Swipe down to open the Quick Settings, tap the icon for Bedtime mode, use back button (or swipe up) to close the Settings. In order to do that I use an Accessibility Service, which you have to enable if you want to use the feature (see instructions). It is experimental because all I can do is perform the gestures and hope everything went alright, no way to really confirm that Bedtime mode is actually on or off (that I know of at the moment).
I made a video that demonstrates both the 2-way synchronization of the DND state and the Bedtime mode feature:
Last but not least a little Disclaimer: I'm not very experienced in Android App Development and I've never released an App before. Even though it works fine for me I have no idea what might happen on other systems and configurations, so please be gentle
I'm happy to hear your thoughts, feedback, ideas, bug reports and I will see if I can do something about it.
Let me know if you have any questions!
Stay safe!
Looks good, I'm going to install. Using watch4 and OnePlus 8T running Pixel experience rom. Will report back.
I'm wondering if this will work with the silent and vibrate function of the switch on the side of the 8T because that switch doesn't use DND
If possible it'd be cool if you made an option for that in the app
spart0n said:
Looks good, I'm going to install. Using watch4 and OnePlus 8T running Pixel experience rom. Will report back.
I'm wondering if this will work with the silent and vibrate function of the switch on the side of the 8T because that switch doesn't use DND
If possible it'd be cool if you made an option for that in the app
Click to expand...
Click to collapse
Cool thanks!
The app listens to DND changes so I think your scenario won't trigger the sync but I can look into it and I guess it's doable, but I have to have a closer look first.
So the switch on your phone toggles between silent, vibrate and sound? And you would like the watch to mirror this mode instead of DND? Just to make sure I understand you correctly.
rhaeus said:
Cool thanks!
The app listens to DND changes so I think your scenario won't trigger the sync but I can look into it and I guess it's doable, but I have to have a closer look first.
So the switch on your phone toggles between silent, vibrate and sound? And you would like the watch to mirror this mode instead of DND? Just to make sure I understand you correctly.
Click to expand...
Click to collapse
You got that exactly right! You rock!
There is an app similar to this one: https://play.google.com/store/apps/details?id=se.blunden.donotdisturbsync
It doesn't work for me, though (Pixel 3, stock software). that app had the limitation of only syncing one way (watch to phone) - is the other direction (phone to watch) what the adb command is for?
tinuthir said:
There is an app similar to this one: https://play.google.com/store/apps/details?id=se.blunden.donotdisturbsync
It doesn't work for me, though (Pixel 3, stock software). that app had the limitation of only syncing one way (watch to phone) - is the other direction (phone to watch) what the adb command is for?
Click to expand...
Click to collapse
Yes, I saw this app but I never actually tried to use it tbh, mainly because I wanted the Bedtime feature and a new challenge The adb command this app uses didn't work when I tried it on my watch. The app was develped for Wear OS 2.0, so my guess is that's why the command doesn't work. I found a different command that works for me on the new OS.
Exactly. In order to control the DND state the app needs the permission from the user. On the phone it's not a problem to grant it but on the watch there is no UI for the user to grant it, the adb command gives the permission to the app. Without it the app can't change the DND state and that's why phone->watch does not work.
Great job...
I don't have my watch4 yet but DND was one of the things I was going to look into but I guess no need to rush anymore...
Also, since you made it and you never released an app before, I hope you signed your apks with release-keys of your own, it will maintain the integrity of the apks whether you release any new version or not, no one can abuse your apks to release updates that can actually update your original work and overwrite it...
Just a dev looking after another ...
Take care and cheers
Dante63 said:
Great job...
I don't have my watch4 yet but DND was one of the things I was going to look into but I guess no need to rush anymore...
Also, since you made it and you never released an app before, I hope you signed your apks with release-keys of your own, it will maintain the integrity of the apks whether you release any new version or not, no one can abuse your apks to release updates that can actually update your original work and overwrite it...
Just a dev looking after another ...
Take care and cheers
Click to expand...
Click to collapse
Thank you so much for your kind words!
I used the signing functionality from Android Studio and in the process I created keys, so I hope that I did the right thing there.
spart0n said:
You got that exactly right! You rock!
Click to expand...
Click to collapse
Hey, I want to give you a little update: I looked into it and of course I hit a few road blocks, thanks Android..
The battery optimizations introduced in Android 8 make it a bit more difficult than before to listen to the ringer mode changes. I think I found a way to do it, but I'm not sure if or how it will impact battery life, but I think I'm optimistic on that one. Another problem I'm facing is coming from the Android API. When I use the API to enable silent mode it just triggers DND, which is really annoying and I believe it should not? And I believe it is not what your phone is doing and what you are looking for. I've seen people complaining about that in forums but at this point I'm not sure how to deal with this. So overall I get the feeling I'm kind of fighting the Android System at the moment
Also, sorry for the long delay, I don't have a lot of time at the moment since I really should focus on my upcoming exams
Cheers!
rhaeus said:
Hey, I want to give you a little update: I looked into it and of course I hit a few road blocks, thanks Android..
The battery optimizations introduced in Android 8 make it a bit more difficult than before to listen to the ringer mode changes. I think I found a way to do it, but I'm not sure if or how it will impact battery life, but I think I'm optimistic on that one. Another problem I'm facing is coming from the Android API. When I use the API to enable silent mode it just triggers DND, which is really annoying and I believe it should not? And I believe it is not what your phone is doing and what you are looking for. I've seen people complaining about that in forums but at this point I'm not sure how to deal with this. So overall I get the feeling I'm kind of fighting the Android System at the moment
Also, sorry for the long delay, I don't have a lot of time at the moment since I really should focus on my upcoming exams
Cheers!
Click to expand...
Click to collapse
Silent can be DND just not vibrate. So that should help you. Also you're awesome for working on this
Just installed this on my GW4 working with my Oneplus 8T. Seems to be working great. Definitely willing to test out any additional changes you may require. In any case, like to say kudos, for developing this.
Pixel 3 and GW4 Classic - DND Sync works perfectly. Bedtime mode, however, does not if you (as I did) reassigned the quick settings buttons.
I now made sure that DND is quick setting button 1 and bedtime mode is button 2, but it's still hit or miss. Sometimes, the swipe gesture isn't performed and I can't quite see why that is.
Edit: one other gripe I have is that bedtime mode gets activated on the watch when I flip my phone over (the setting on the phone is "flip to shhh". That's no good for me, so I turned bedtime mode sync off completely. I still use the dnd sync portion though!
However, I'm already quite enjoying this a lot, DND sync alone is well worth the app. I'd encourage everyone to check it out!
Just posting to see, for those using this, if they are experiencing the watch getting out of sync with the phone. This had been working reliably up until the latest watch update as far as I can tell. Now there are several instance of DND still being on on the the watch, while my phone has disabled DND. Also wise versa, not on while phone has going to DND per schedule. Curious if others have seen the same. I have also noticed that DND/Bedtime mode no longer dims the screen on the watch like it use to, but I believe that a Samsung issue. In any case, curious if anyone else experiencing the same and or if perhaps new version in the works. Again, this had been working great; really liked this app. Hope development hasn't been abandoned.
Note: I just uninstalled and reinstalled on both watch and phone to see if maybe something got screwed up with the watch version update. Will see
Hi there, i´m trying to install this but i got lost on Github, where can i fand apks?
Edit: nevermind, i found it and works excellent dnd sync on pixel 4 xl, thanks a lot
Figured I'd report back that the app is working perfectly again after the reinstall. My guess is that the update on the watch must have reset the permissions or something. In any case, figured I share in case anyone else experiences the same. Happy it's working reliably again.
Excuse me, why does my watch always turn on and off automatically
@rhaeus is there any way to make an app or your app sync alarms from watch to phone and be able to snooze or disable them and have it sync between both devices? This was possible when using a Samsung phone with the Active2.
rhaeus said:
Hello everyone!
I'm using the Samsung Galaxy Watch 4 with a Pixel 3a XL and I was a bit annoyed that the option to synchronize the Do Not Disturb (DND) state between watch and phone seems to be only available when paired to a Samsung phone. So I made an App to fix this and I'd like to share it with as many people as possible (I don't know how much interest there is).
View attachment 5398215View attachment 5398217View attachment 5398219View attachment 5398221
As for now it is not in the Google Play Store but you can find the APK files, instructions and the source code on my GitHub.
Besides the DND sync I also implemented to (optionally) toggle Bedtime mode on the watch depending on the DND state of the phone (this is a bit experimental though, since I had to use an Accessibility Service for that, more on that below).
The installation on the watch is a bit technical (needs ADB) and here I want to explain why it is how it is.
Why do I need ADB?In order to listen to DND changes and also change the DND state, the app needs the permission from the user. On the phone it is no problem to grant said permission (it's the ACCESS_NOTIFICATION_POLICY for those curious) because the system provides a permission screen where the user can handle that permission. On the watch this screen is missing and therefore the user can't grant the permission to the watch. That's where ADB comes into play. I found a command which allows to enable the permission for the app via ADB. (I could only test this with my watch, I think (and hope) it will work on other devices too) In order for the app to work properly, you have to execute this command once after installation. The details are in the GitHub instructions.
Why is Bedtime mode experimental?In an ideal world I would know a command to use in my program that controls the Bedtime mode setting directly. Unfortunately I haven't found such a command (if anyone knows, please let me know). As a workaround I figured I could simulate the touch gestures which you would use to do it manually: Swipe down to open the Quick Settings, tap the icon for Bedtime mode, use back button (or swipe up) to close the Settings. In order to do that I use an Accessibility Service, which you have to enable if you want to use the feature (see instructions). It is experimental because all I can do is perform the gestures and hope everything went alright, no way to really confirm that Bedtime mode is actually on or off (that I know of at the moment).
I made a video that demonstrates both the 2-way synchronization of the DND state and the Bedtime mode feature:
Last but not least a little Disclaimer: I'm not very experienced in Android App Development and I've never released an App before. Even though it works fine for me I have no idea what might happen on other systems and configurations, so please be gentle
I'm happy to hear your thoughts, feedback, ideas, bug reports and I will see if I can do something about it.
Let me know if you have any questions!
Stay safe!
Click to expand...
Click to collapse
Hello. where is the application itself?
shaker74 said:
Hello. where is the application itself?
Click to expand...
Click to collapse
In the post you quoted it says they are on his GitHub and there is a link to it.
shawkes said:
In the post you quoted it says they are on his GitHub and there is a link to it.
Click to expand...
Click to collapse
I looked there, I did not find any apk applications