After flashing Oreo into my S8+ (SM-G955FD) Via Odin, I've noticed that my Bixby wake-up command has completely killed itself, I've also received the new update that was rolled out a day or two ago, which is what I was waiting for before posting regarding it here; I know that many do not really care about Bixby but it happened to be quite useful to me, especially because I have to set Google Assistant as my "Default Assistant App" in order for its voice commands to work unlike Bixby but that's for my own personal preference, so I've tried to clear data on every Bixby applications and re-doing all of the voice training, it didn't do the job however there is something I've noticed when I attempt to get Bixby by voice command, in the notification tray there is a notification of Bixby indicating that it's supposedly waking up (Screenshot is included.)
{
"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"
}
So that's all I have, if anyone can assist me on how this can be resolved, I'd really appreciate.. Nobody else has complained about this issue and I don't know if that's whether if people don't care or perhaps this is ONLY ME, which worries me so please, thank you in advance.
Whoops.
Seems like I cannot post images yet, but It's practically the new Oreo functionability which shows any applications that "display over screen".
DrNipz said:
After flashing Oreo into my S8+ (SM-G955FD) Via Odin, I've noticed that my Bixby wake-up command has completely killed itself, I've also received the new update that was rolled out a day or two ago, which is what I was waiting for before posting regarding it here; I know that many do not really care about Bixby but it happened to be quite useful to me, especially because I have to set Google Assistant as my "Default Assistant App" in order for its voice commands to work unlike Bixby but that's for my own personal preference, so I've tried to clear data on every Bixby applications and re-doing all of the voice training, it didn't do the job however there is something I've noticed when I attempt to get Bixby by voice command, in the notification tray there is a notification of Bixby indicating that it's supposedly waking up (Screenshot is included.)
So that's all I have, if anyone can assist me on how this can be resolved, I'd really appreciate.. Nobody else has complained about this issue and I don't know if that's whether if people don't care or perhaps this is ONLY ME, which worries me so please, thank you in advance.
Click to expand...
Click to collapse
I dont like BIXBY sorry
Inviato dal mio SM-N950F utilizzando Tapatalk
:/
Bumppp
SO DONE.
I guess nobody really cares about this but I am as desperate as ever but I guess I'll have to go on without Bixby until they give another update which I don't know how long it might take, I've talked to several Samsung support agents and all I've got from them is stupid normie solutions that'll make you question how they got the job for that position, the "turning it off and on" meme is real and so annoying because they do not understand and will not even try to understand the issue and go on with their automated solutions that probably only help old white people trying to understand technology and apparently the support fails to tell them apart, I am absolutely livid after this horrible experience with Samsung, after hours of trying to make them understand, one understood and understood it so much that he realized he cannot help me at all and said that this is so technical that I'll have to either wait for an update which may or may not fix this or literally throw away my phone aka go get it replaced under warranty which is totally absurd.
I have the same problem, bixby just wont wake up, the icon pops on notification bar then disappears. Still cant find a solution
Edit: wirdly enough i just called it and it responded everything is working well, i dont know if its because of the CRB7 update. It just worked on its own
ModekXKay said:
I have the same problem, bixby just wont wake up, the icon pops on notification bar then disappears. Still cant find a solution
Edit: wirdly enough i just called it and it responded everything is working well, i dont know if its because of the CRB7 update. It just worked on its own
Click to expand...
Click to collapse
I have done enough research on my own phone and the only moment Bixby voice has worked for me is when I reboot and keep saying "Hi Bixby" and it will suddenly work for at least 5-10minutes depending on what triggers it to not work, and I can't seem to figure what does that, because this has to do with some other software interrupting Bixby to show over screen because it's obviously reacting to you when you say Hi Bixby in the notification bar, so please let me know if it's working fine for you now regardless?
Update : Bixby Voice just received a new update 1.0.19.10, and yet it has not fixed the issue for me and I have also realized that Bixby works perfectly when in Safe mode so it could be a third-party app interfering as well.
DrNipz said:
I have done enough research on my own phone and the only moment Bixby voice has worked for me is when I reboot and keep saying "Hi Bixby" and it will suddenly work for at least 5-10minutes depending on what triggers it to not work, and I can't seem to figure what does that, because this has to do with some other software interrupting Bixby to show over screen because it's obviously reacting to you when you say Hi Bixby in the notification bar, so please let me know if it's working fine for you now regardless?
Update : Bixby Voice just received a new update 1.0.19.10, and yet it has not fixed the issue for me and I have also realized that Bixby works perfectly when in Safe mode so it could be a third-party app interfering as well.
Click to expand...
Click to collapse
Could be, try messing with overlay permitions and administrator.
ModekXKay said:
Could be, try messing with overlay permitions and administrator.
Click to expand...
Click to collapse
I have fixed as it seems so far.. I started to uninstall unwanted apps to any suspicious apps, and I do not know which one but if you have any shady apps such as WPS testing app or anything related to such uninstall, anyways here is what I did; SafeMode>Settings>Device Assistant > Select none > then boot into normal > wait for Bixby to work > go into device assistant> pick Google back as assistant. That's all I did.
Okay, I was wrong after almost 24hours of using my phone with Bixby working it has suddenly again stopped working after I updated some apps on the PlaysStore, this issue seems very complex with no logic behind it, it's quite annoying..
Hi .. i have the same pb with my note 8 .. it had appeared after installed the android 8
Lets switch S8's
DrNipz said:
After flashing Oreo into my S8+ (SM-G955FD) Via Odin, I've noticed that my Bixby wake-up command has completely killed itself, I've also received the new update that was rolled out a day or two ago, which is what I was waiting for before posting regarding it here; I know that many do not really care about Bixby but it happened to be quite useful to me, especially because I have to set Google Assistant as my "Default Assistant App" in order for its voice commands to work unlike Bixby but that's for my own personal preference, so I've tried to clear data on every Bixby applications and re-doing all of the voice training, it didn't do the job however there is something I've noticed when I attempt to get Bixby by voice command, in the notification tray there is a notification of Bixby indicating that it's supposedly waking up (Screenshot is included.)
So that's all I have, if anyone can assist me on how this can be resolved, I'd really appreciate.. Nobody else has complained about this issue and I don't know if that's whether if people don't care or perhaps this is ONLY ME, which worries me so please, thank you in advance.
Click to expand...
Click to collapse
I honestly think your in a better situation than most.
I do not know of any one who likes BIXBY.
I do like bixby.
I'm don't seem to have any real problems with bixby on Oreo. I problem I have is try to create quick commands.
If I say "Hi Bixby" it will open,
Then I can say Open "xda" and it will open.
Now say I want to go to the subscribed threads in the app.
with the app opened, I say "Hi Bixby" go to subscribed threads. It will not do it, but with the app opened I can press the bixby key and say subscribed threads and it will go to the threads. why?
DrNipz said:
After flashing Oreo into my S8+ (SM-G955FD) Via Odin, I've noticed that my Bixby wake-up command has completely killed itself, I've also received the new update that was rolled out a day or two ago, which is what I was waiting for before posting regarding it here; I know that many do not really care about Bixby but it happened to be quite useful to me, especially because I have to set Google Assistant as my "Default Assistant App" in order for its voice commands to work unlike Bixby but that's for my own personal preference, so I've tried to clear data on every Bixby applications and re-doing all of the voice training, it didn't do the job however there is something I've noticed when I attempt to get Bixby by voice command, in the notification tray there is a notification of Bixby indicating that it's supposedly waking up (Screenshot is included.)
So that's all I have, if anyone can assist me on how this can be resolved, I'd really appreciate.. Nobody else has complained about this issue and I don't know if that's whether if people don't care or perhaps this is ONLY ME, which worries me so please, thank you in advance.
Click to expand...
Click to collapse
Question, did you flash all the files included in the update?
Reson i asked is because i had the same issue, i got in touch with samsung, but after getting into my phone and not fixing the issue, i remembered i had omited one of the files in the update, (i think i missunderstood a post or something), i reflashed ALL the files in the update, aparently it did not work, but then i went into apps 3 dots show system apps, from the list of apps i located ALL the Bixby apps i counted 6, got into Storage and cleared the data from all 6, i restarted, bixby and it worked.
No clue I disabled it
I finally received the Sprint Oreo update I'm having the same problem so it's probably not a problem with you flashing it. I usually use a combination of Bixby and Google Assistant.
Edit: If you wipe cache partition, it will work again but then stop.
I have the same exact problem
tnbx said:
I have the same exact problem
Click to expand...
Click to collapse
I have figured out how to resolve this without factory reset, please look for my thread on r/GalaxyS8, my username is the same as here.
Never had any issue when I updated to oreo it works just the same as always
DrNipz said:
I have figured out how to resolve this without factory reset, please look for my thread on r/GalaxyS8, my username is the same as here.
Click to expand...
Click to collapse
I can't find it
---------- Post added at 11:45 PM ---------- Previous post was at 11:36 PM ----------
DrNipz said:
I have figured out how to resolve this without factory reset, please look for my thread on r/GalaxyS8, my username is the same as here.
Click to expand...
Click to collapse
I've found it thank you , been like 2 months I don't use it , kinda gave up trying but now it's fixed thank u
Turning off microphone permissions on some apps did the trick ??????
---------- Post added at 11:50 PM ---------- Previous post was at 11:45 PM ----------
Just wanna share a way to remap the Bixby button without "calling" the Bixby app , it just needs adb permissions with a command no root needed ???
https://play.google.com/store/apps/details?id=flar2.homebutton
Related
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
Since taking 4.4.4 (and rooted), I have been unable to record any video in either the stock app or the google camera (haven't tried any 3rd party beyond that). Pictures are fine, but trying to take any video with the moto stock camera gives the following error msg on screen:
"Not able to start video capture"
{
"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"
}
Google camera gives no error, just wont record. I have tried clearing cache and data, reboots, etc. So far, I have no insight into whats causing this. Anyone else out there seen this?
Thanks
Open the Google app. Scroll all the way to the bottom and hit the three dot menu control bottom right, then settings. Go to voice, then OK Google detection. Turn it off
L7iharsha said:
Open the Google app. Scroll all the way to the bottom and hit the three dot menu control bottom right, then settings. Go to voice, then OK Google detection. Turn it off
Click to expand...
Click to collapse
Yep. That was it. Is this a known issue? I searched and searched but came up with nothing. Many thanks.
buddhatown said:
Yep. That was it. Is this a known issue? I searched and searched but came up with nothing. Many thanks.
Click to expand...
Click to collapse
Yes it is.
Didn't work for me!
L7iharsha said:
Open the Google app. Scroll all the way to the bottom and hit the three dot menu control bottom right, then settings. Go to voice, then OK Google detection. Turn it off
Click to expand...
Click to collapse
Did not work for me! I have a Motorola Maxx XT1080 with 4.4.4. Upon re-boot, video capture works first time, but fails every time thereafter with error message "Not able to start video capture". If I re-boot again, same thing...works once, then fails thereafter with same error message. Any other solutions?
buddhatown said:
Since taking 4.4.4 (and rooted), I have been unable to record any video in either the stock app or the google camera (haven't tried any 3rd party beyond that). Pictures are fine, but trying to take any video with the moto stock camera gives the following error msg on screen:
"Not able to start video capture"
View attachment 2874053
Google camera gives no error, just wont record. I have tried clearing cache and data, reboots, etc. So far, I have no insight into whats causing this. Anyone else out there seen this?
Thanks
Click to expand...
Click to collapse
Updated to 4.4.4 and I got the same problem
Thanks for that, been wondering what the issue has been. I guess I will just keep it so that my Nova Launcher has the Ok Google response. Turned off the Google one and it fixed the issues for the phone now. Much appreciated for the help.
Had this same problem.
I was taking videos this evening with no problems then started checking out "Google Now" options and enabled the voice commands from any app and from the locked screen. Then went back to taking or trying to take videos and got this same error message. I tried rebooting and it didn't work so I googled the error message and found this forum. I did as suggested and disabled the voice commands for "Google Now" and my video recording went back to working. So does anyone know if this error is being addressed for a fix? Also, thanks for the help!
**** that, I was wondering what was wrong with my droid ultra, well i dont even need the okay google command since we have touchless controls anyways so its pretty pointless, also seeing how we may get updated to the new moto actions.
moto x xt1058 video capture not able
Hello friends, some time ago I got moto x xt1058, update to 4.4.4 and get same problem
Camera work well after reboot, but then I get message "not able to start video capture". That to bad course Skype and viber also didn't work.
Then I find this forum and try to turn off OK google now detection, but this button in voice google app's menu didn't work. It is grey (not active) color and has a message below " this feature is currently anavaliable on this device". Google now voice commands works well and I have no idea how to fix my camera problem.
P.s. camera work only in slow mode.
Thanks.
HERE IS THE FIX! Remove call recorder.
I HAD THE SAME THING for the last 3 months. I found it v frustrating.
THIS FIXED IT FOR ME AND FOR OTHERS
REMOVE THE APP CALLED "CALL RECORDER" as this uses the microphone at all times and stops video from working. Other call recorders seem to work fine with no affect on video.
Cheers,
Ben
Ben's Awesome Solution to "not able to start video capture" on my Moto X
I have had the same problem as many others.
Where I try video recording on my Moto X and only get the SUPER FRUSTRATING - "not able to start video capture"
I tried the Google "3 Dot" - Google Now Shut Down and it worked upon reboot..."ONCE." Only to have it not work until another reboot...
I had to resort to carrying around a spare iphone to record what my Moto X couldn't.... auuggghhhh!!
Anyways, to make a long story short, Ben's comments fixed my problem...
lifemac3 said:
I HAD THE SAME THING for the last 3 months. I found it v frustrating.
THIS FIXED IT FOR ME AND FOR OTHERS
REMOVE THE APP CALLED "CALL RECORDER" as this uses the microphone at all times and stops video from working. Other call recorders seem to work fine with no affect on video.
Cheers,
Ben
Click to expand...
Click to collapse
After I deleted this app...NOW I have use of my Video Camera and DO NOT GET THE "not able to start video capture", AND I just tried to set up Smartphone payments with Square.com (the app would not work with the swiping Dongle because it said "A RECORDING APP NEEDED TO BE CLOSED" for that process to occur) which lead me on another internet search for a solution and wound me up backtracking to here and eventually to Ben.
So now I can Take Videos and charge people for them??? Ha ha, Maybe I will now!! Who Knows!! ;P
Thanks Ben for your AWESOME Solution!!!
REMOVE THE APP CALLED "CALL RECORDER" as this uses the microphone at all times and stops video from working. Other call recorders seem to work fine with no affect on video
~~~~~~ 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!
On the lock screen a full screen ad appears within 3 seconds. I hate it. Is this normal?
I've tried disabling a bunch of stuff,changing permissions, notification options, etc, nothing seems to get rid of it. Anyone else had this issue, and found out what causes it or find a way to fix it?
Not normal. At least it wasn't for me (U11 Unlocked)
On other phones, this was usually due to either ES File Explorer or any of the GO apps like GOSMS, etc. Try uninstalling those if you have them.
News Republic is known to serve ads too. you mind showing the ad on your lockscreen? Some of them contains hints of which app is serving them.
Also include a list of apps so maybe we can identify which is the culprit if any of us tried it before.
Conan1986 said:
News Republic is known to serve ads too. you mind showing the ad on your lockscreen? Some of them contains hints of which app is serving them.
Also include a list of apps so maybe we can identify which is the culprit if any of us tried it before.
Click to expand...
Click to collapse
I think I found what the problem is while looking on the Play store at the Sense Home app. Different ad, but same thing.
{
"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 could be wrong because I'm not very smart, but I think this means its baked into the launcher, with no option to actually stop it. Tried clearing all app data, cache etc in airplane mode so it can't get more ads fed to it, but it's still there. Even tried to switch to a standard google launcher but even that didn't get rid of it.
I'm still hopeful that I'm missing something simple here, but also worried that HTC are being giant a-holes forcing ads and not allowing options to remove. Anyone have any other ideas?
By any chance do you have the Yelp App? LOL
also you could try
Settins/Sound ¬ifications/On the lock screen/
Don't show notifications at all
or go to Blinkfeed. Click the + sign and uncheck Mealtime recommendations.
Could just be sense home. Have you tried to disable ads in the launcher? If it still happens, then it's a third party app causing the lockscreen ads.
In order to get rid of notification apps that pop up in the upper left corner, all you have to do is swipe down to show the ads, then longpress on the particular app thats really pissing you off, and a menu will show and then select "never show again". That news republic used to piss me off all the time when it pops up and there was no other way to get rid of it. Its gone now,,,,lol. Anyway, try that method.
Av8ter said:
In order to get rid of notification apps that pop up in the upper left corner, all you have to do is swipe down to show the ads, then longpress on the particular app thats really pissing you off, and a menu will show and then select "never show again". That news republic used to piss me off all the time when it pops up and there was no other way to get rid of it. Its gone now,,,,lol. Anyway, try that method.
Click to expand...
Click to collapse
I can't do that because it's on the lock screen
spikeydoo2006 said:
Could just be sense home. Have you tried to disable ads in the launcher? If it still happens, then it's a third party app causing the lockscreen ads.
Click to expand...
Click to collapse
Thanks, have done all that and more. Has to be something else then .
schmeggy929 said:
By any chance do you have the Yelp App? LOL
also you could try
Settins/Sound ¬ifications/On the lock screen/
Don't show notifications at all
or go to Blinkfeed. Click the + sign and uncheck Mealtime recommendations.
Click to expand...
Click to collapse
Thanks. I don't have yelp, and have tried that setting. Don't have meal recommendations on either.
OK I think I fixed it now. Pretty annoying.
It's counter-intuitive, but I had to actually enable mealtime recommendations in blinkfeed so that all the other stuff I turned off could override it, for some stupid reason.
Scratch that. It somehow un-fixed itself. This is driving me insane!!
Something to do with HTC and Yelp being in bed with each other, as I don't have yelp or anything on my phone. It still shows up whether I have mealtime recommendations or ads allow or disallowed or any combination of the above.
Be good if they would provide a simple/transparent way of blocking this s#!t. I really can't think of anything else to try.....
It's not news republic? That's the only thing I've seen do that
JarJar9 said:
On the lock screen a full screen ad appears within 3 seconds. I hate it. Is this normal?
I've tried disabling a bunch of stuff,changing permissions, notification options, etc, nothing seems to get rid of it. Anyone else had this issue, and found out what causes it or find a way to fix it?
Click to expand...
Click to collapse
Yeah i got that the one time i signed into HTC account and turned on location for it. It started giving me lunch time recommendations etc. I dont normally use HTC account, just google, but thought i would try it on 11. Quickly did new setup and didn't sign in to HTC.
purple patch said:
Yeah i got that the one time i signed into HTC account and turned on location for it. It started giving me lunch time recommendations etc. I dont normally use HTC account, just google, but thought i would try it on 11. Quickly did new setup and didn't sign in to HTC.
Click to expand...
Click to collapse
Thanks for that. Worked. I had to go though sense companion setup again to remove the account, but it worked. Took a bit of time afterwards for the ad to disappear, but it hasn't come back since.
Flashlight
I have an HTC U11 that started showing full screen ads (after about 3 seconds viewing the lockscreen, an ad appears suggesting a nearby restaurant) on the lockscreen. After trying everything I found online, I finally took someone's advice and disabled the Flashlight app. Yes, the Flashlight app that's installed when you get the phone. I didn't think it would work, but it did. Give it a try.
I have flashlight installed and use it multiple times a day via the squeeze function... I'd be very surprised if it's that.
Op, post a screenshot of all your installed apps if this problem still persists.
It sounds like you may have already figured it out. But this is likely the Sense Companion app. Which you can disable under settings - apps.
To my knowledge, the Sense Companion is what causes the lock screen suggestion that is pictured in the OP's screenshot.
Edit: Didn't realize that I repeated the post from the person above me.
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