Related
Here is an application to make specific programs(like ebook reader,SatNav etc) prevent standby when they are running. It will watch them even when they are in background, so be careful, if you just forget them running in the background, your phone will not go into standby. (v1.1 change: now you can disable background watch by checking "monitor active window only")
Installation:
1- Just install the latest cab file onto Device Memory and NOT Storage Memory.
2- You need .NETCF 3.5, if you don't have it, install it.
Usage:
1- If you will use background watching, find the executable name from Task Manager/Processes, drop .exe part, type it into textbox and click add. (AdobeReaderLE.exe -> AdobeReaderLE)
1a- If you want to watch only the active window (so that your battery doesn't drain if you minimize the whitelist app) Find the window title of the application (Either task manager/applications or just look at the title if it is not hidden) and insert it as above. (Adobe Reader LE this time) you can have both versions live together. There is one limitation to active application watching though, if the application doesn't report a window title in task manager, you can only background watch it. (e.g. htcreader)
2- if you want to remove a certain app, select its name and click remove button.
3- if you want to have KeepAwake open but still not active (to force into standby) click stop.
4- this app autostarts with each boot, if you don't like it, delete the shortcut under \Windows\Startup\KeepAwake.lnk
5- this app starts minimized. if you want to configure settings, select the icon one more time or switch to it using a task manager.
6- if you click quit, obviously the software quits and no more monitoring is done, so click X after configuring if you want it to monitor your apps.
7- if you want to turn off screen and lock keys (for listening to music maybe) you can click the lock button. If your app is running, the phone will still stay awake.
Tips:
1- You can map KeepAwake to a hardware button for easy access and screen locking.
Credits:
Thanks goes to Frank T. van de Ven for ProcessCE library.
Thanks a lot to DaveShaw for letting me use xdaShutdown application.
I'm pretty excited about this... I've been looking for something exactly like this to prevent specific standby times.
I hope it works with most of the applications I have in mind.
Any bugs? Would you guys find it useful to have a lock button so that it turns off the screen and locks keys but still keeps the device awake? I have implemented this for the latest version I'm using (to have my GPS logger going but preventing accidental touch on screen and keys.) Or is it better to keep it simple?
Will this also prevent Windows MSN not to idle which will cause lost connection too?
Sorry, I'm new to the WinMo scene, just saw this on Pocketnews. Let me get this straight, will this work for apps that run in the bg that don't close out IE:
Facebook
Google Maps
Email
Albums
etc.?
because they slow down my phone, I want to close them out completely, not run them in the background so they can take up valuable resources.
espaleena said:
Will this also prevent Windows MSN not to idle which will cause lost connection too?
Click to expand...
Click to collapse
I haven't specifically tried MSN app, but I see no reason it shouldn't work.
Raadius said:
Sorry, I'm new to the WinMo scene, just saw this on Pocketnews. Let me get this straight, will this work for apps that run in the bg that don't close out IE:
Facebook
Google Maps
Email
Albums
etc.?
because they slow down my phone, I want to close them out completely, not run them in the background so they can take up valuable resources.
Click to expand...
Click to collapse
I think you need a task manager so that you can close apps. This one is for making certain apps prevent the phone go standby.
ozkaya said:
Any bugs? Would you guys find it useful to have a lock button so that it turns off the screen and locks keys but still keeps the device awake? I have implemented this for the latest version I'm using (to have my GPS logger going but preventing accidental touch on screen and keys.) Or is it better to keep it simple?
Click to expand...
Click to collapse
I haven't given this a try yet, but any more additions are welcomed! This is something I've been looking for. I think it might be nice to give a way to put settings per application for standby perhaps (like some applications don't let the device go to stand by for 3 minutes, others are like 30 miuntes, etc). I think having't the screen off is a good addition, but keeping the device working is good, so things like voice recorder can work without having the screen on.
Seems to work well for IM services.
I haven't tested it completely for Opera and internet-browsing programs.
Nevertheless, this is a great idea.
new version is up..
What about on option... KEEP IT ON ? (Like LOCK)
This option would simply keep the phone ON, if the application is running in background even if we haven't listed anything
Is it possible? Maybe it's already included?
Thank you
Great app !
It doesn't work on my HD2. Youtube is running and my device locks and stops YT...
Any ideas??
Zepiii said:
What about on option... KEEP IT ON ? (Like LOCK)
This option would simply keep the phone ON, if the application is running in background even if we haven't listed anything
Is it possible? Maybe it's already included?
Thank you
Great app !
Click to expand...
Click to collapse
I thought about that but later decided that not many people would find it useful. if enough request comes, I will add it. In the meantime, you might just add an always running app like device or cprog into list manually when you want to keep it on always. or just minimize an app in the whitelist
Quider said:
It doesn't work on my HD2. Youtube is running and my device locks and stops YT...
Any ideas??
Click to expand...
Click to collapse
that's odd. I just tried and Youtube keeps itself open while playing a video for me even without this app. (Locks on the search screen) But still, KeepAwake seems to detect it when it is running. After installing have you clicked on the icon to run KeepAwake? Then minimized it by clicking on X? Have you tried another app, like Adobe Reader for instance? Is youtube minimized or active?
Hi,
Will this application disable lock option on device while using some application - eg. iGO Navigation?
Thanks
mdzepinajr said:
Hi,
Will this application disable lock option on device while using some application - eg. iGO Navigation?
Thanks
Click to expand...
Click to collapse
as long as you don't lock it yourself, yes, it won't be locked.
Very nice app...much thanks!
The app works for eReader on my Omni II running 6.3 One word of caution I have the x= app closed option turned on so the x shuts down keepAwake. It took me some time to figure out I was closing the app not minimizing it.
How would I go about disabling the standby while in a call? What's the name of the application I need to put in there? I'd like to use it so the sleep during call doesn't stop the call recording utility from working, but I still would like the screen turning off when keeping the phone at the ear.
Doesn't work on touch pro2
The software breaks error when we try to add software to the list, only with the program in background it goes to sleep anyways. It's a good idea, but not there yet...
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
danlo said:
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
Click to expand...
Click to collapse
Were you using headphones that day? I've seen this issue, and I think it's an audio issue (software). When I had this issue, the speakers didn't work either.
Sent from my Nexus 5 using Tapatalk
I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
TJCacher said:
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip!
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
I've had the same issue, but I can add that this is happening with games as well. Specifically, asphalt 8 causes this problem. Obviously, when I'm switching between apps, I wouldn't want to kill an ongoing game or song just to make the hotword work. The HC issue is annoying and I hope there's a fix to always keep it live no matter which apps are in the background...
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
My hotword detection also suddenly doesn't work. I've toggled the option in google now settings, rebooted, cleared cache, turned off google music... nothing turns it back on.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
didn't help me. can't figure out what is going on. so frustrating.
---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
gaetawoo said:
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
Click to expand...
Click to collapse
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
TJCacher said:
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've talked to them, they know about it and are working on it, but that say it could be an OS issue.. that are trying to figure it out.
This happens to me at least couple times a day. Either Wi-Fi disconnect or a OK Google three I n a row consecutive search. Solution: kill the g search app it will automatically restart and you'll be gtg
Pebble whatsapp notifier causes this same problem. Unchecked it in accessibility and viola! Always listening again..
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
I have the same issue and none of that work for me, it gets stuck with real racing, i force the stop once and it started to work again but minutes later it was hallow again, please help
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
Are you on stock? I thought this was a result of the new launcher in today's version of cm.
Sent from my Nexus 5 using XDA Premium 4 mobile app
xdapro said:
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
Click to expand...
Click to collapse
I love you dude or dudette I was going balled trying to figure this out, thanks a lot!
I found out that the hot word detection only works on the default launcher. If I add the google search widget on apex launcher, I get the search bar with a hollow mic, and hot word detection does not work.
If I use default launcher I got the full mic and hot word detection works.
Sent from my Nexus 5 using xda app-developers app
Android Wear voice action to play music only works if the phone screen is on & unlock
Using Android Wear voice command "listen to..." or "play ..." will basically queue up my music and won't start playing until I unlock and/or turn my screen on. I've spent a bunch of time trying different music on my phone locally and streaming and each time I have to have my phone on for it to start playing. How can I fix this?
legato89 said:
Using Android Wear voice command "listen to..." or "play ..." will basically queue up my music and won't start playing until I unlock and/or turn my screen on. I've spent a bunch of time trying different music on my phone locally and streaming and each time I have to have my phone on for it to start playing. How can I fix this?
Click to expand...
Click to collapse
These could the reasons but I would need more information
Do you have any app which hibernates your apps in deep sleep mode (screen off) Like Greenify /Amplify etc?
Are you on a custom rom ?
do you use battery saver mode while trying this ?
Quote me back in case you expect a reply!
Hnk1 said:
These could the reasons but I would need more information
Do you have any app which hibernates your apps in deep sleep mode (screen off) Like Greenify /Amplify etc?
Are you on a custom rom ?
do you use battery saver mode while trying this ?
Quote me back in case you expect a reply!
Click to expand...
Click to collapse
I do not use Greenify /Amplify. The only app I have that's close or allows changes to how my phone behaves is 3C Toolbox, and I haven't enabled or changed anything in that app.
I do not use a custom ROM. I am stock rooted on the Tmobile ROM, so locked bootloader.
I have turned off stamina mode, which I have set to activate at 15% anyway, with the same results.
legato89 said:
I do not use Greenify /Amplify. The only app I have that's close or allows changes to how my phone behaves is 3C Toolbox, and I haven't enabled or changed anything in that app.
I do not use a custom ROM. I am stock rooted on the Tmobile ROM, so locked bootloader.
I have turned off stamina mode, which I have set to activate at 15% anyway, with the same results.
Click to expand...
Click to collapse
So according to you, you do not use any battery saving apps or stamina mode neither hibernation apps or any custom ROM or kernel and still you need to turn on screen to run music player. You send commands via your android wear to your phone via bluetooth and both devices are paired. Try removing the toolbox and see any differences ..
Which version of android are you running and secondly have you tried restarting devices and re-pairing as well.
Seems to me some compatibility issues. Are you using stock music player or some different app?
Try google music and see if that helps.
Quote me back for a reply.
Hnk1 said:
So according to you, you do not use any battery saving apps or stamina mode neither hibernation apps or any custom ROM or kernel and still you need to turn on screen to run music player. You send commands via your android wear to your phone via bluetooth and both devices are paired. Try removing the toolbox and see any differences ..
Which version of android are you running and secondly have you tried restarting devices and re-pairing as well.
Seems to me some compatibility issues. Are you using stock music player or some different app?
Try google music and see if that helps.
Quote me back for a reply.
Click to expand...
Click to collapse
Correct. As soon as I turn the display on, Google Play Music is opened ( I can't tell if it loads when I unlock/turn the display on or if it gets that far and doesn't play) and starts playing. I will try removing 3C.
I'm on 5.0.2, the latest Tmobile firmware. I have Google Play Music set as the default action, for that voice action.
After much troubleshooting I was able to find my answer: I need to say either artist+album, artist+song, or Album to get playback to start while the screen is off and phone is locked. Saying "listen to *artist* does not start playback until the screen is turned on, and it appears it will pick a random song to play.
I have a call recorder app and that thing keeps getting terminated even though it's in the protected app list.
Any solution?
Thanks!
It could be that the call recorder app you installed is not support for use with either the current version of android installed on your device, or it's just not compatible with your device entirely.
DarkGuyver said:
It could be that the call recorder app you installed is not support for use with either the current version of android installed on your device, or it's just not compatible with your device entirely.
Click to expand...
Click to collapse
It's this one never had a problem with it with my s7. https://play.google.com/store/apps/details?id=com.skvalex.callrecorder
I disabled battery optimization for this app , i'll see if it helps.
lowspeed said:
It's this one never had a problem with it with my s7. https://play.google.com/store/apps/details?id=com.skvalex.callrecorder
I disabled battery optimization for this app , i'll see if it helps.
Click to expand...
Click to collapse
Try using another call recorder. The current call recorder you are using probably isn't compatible with the Honor 6X.
DarkGuyver said:
Try using another call recorder. The current call recorder you are using probably isn't compatible with the Honor 6X.
Click to expand...
Click to collapse
Actually, i fixed it. The main culprit was the battery optimization
lowspeed said:
Actually, i fixed it. The main culprit was the battery optimization
Click to expand...
Click to collapse
Glad you solved your problem. But I wonder why would the battery optimization software cause problems with the call recorder app that you are using....
guest user doubt
In Honor 6x is guest mode available or not???? and by using only pin can we split two user accounts i.e(user and guest) or else can we use also fingerprint for two users...please reply me back
DarkGuyver said:
Glad you solved your problem. But I wonder why would the battery optimization software cause problems with the call recorder app that you are using....
Click to expand...
Click to collapse
Because it causes the services to be terminated
lowspeed said:
Because it causes the services to be terminated
Click to expand...
Click to collapse
Interesting....
lowspeed said:
I have a call recorder app and that thing keeps getting terminated even though it's in the protected app list.
Any solution?
Thanks!
Click to expand...
Click to collapse
Glad you solved, but you can also lock it in recents to disable from getting stopped.
Try using another call recorder
I know this is an old thread but I'm having the same issue. Even if I lock a program in recent apps, it will still close at some point. I have to reopen my podcast app and pdf reader on a daily basis (sometimes multiple times) And I have battery optimization off.
terryowen said:
I know this is an old thread but I'm having the same issue. Even if I lock a program in recent apps, it will still close at some point. I have to reopen my podcast app and pdf reader on a daily basis (sometimes multiple times) And I have battery optimization off.
Click to expand...
Click to collapse
Go to settings -> Battery -> Close apps after screen lock and untick the apps you dont want the OS to close. I have seen apps running in the background for days, sometimes I even forget that the app was in background until I open it for something.
Yes, I've already done this too. (Sorry for not mentioning it.) It's weird though, it seems like it only keeps the last 3 or 4 recent apps max after a certain period of time. I like this phone but this is one is starting to bug me a lot.
Anyway, Pocket Casts, ezPDF Reader, TuneIn Radio Pro and Music Folder Player all are identified as power intensive and get killed, even if locked and unselected from lock screen close or the power intensive apps screen. I have all power saving options turned off as I rarely get below 70%.
Note: I've been poking around some more and ended up in app settings and in the Advanced/Special Access, it looks there is a "Exempt from battery optimization" section. I'm going to put my reader and music apps in and see what happens.
I can successfully run widgetupdatet and musicproxy on my uis7862 unit.
But I think i need to make it start at boot/wakeup and also make it not battery optimized
So for start at boot/wake up, i turn it on with User - application. But this make widgetupdater app show up everytime when unit boot up, which i prefer it to hidden
For battery optimized setting, I don't have battery option from my setting menu.
May I have your advice on this?
@KёniG
Thanks
Hello.
The newest firmware doesn't have battery settings. Install this https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut and find "Settings suggestions". Launch it and type in the search field "Battery".
KёniG said:
Hello.
The newest firmware doesn't have battery settings. Install this https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut and find "Settings suggestions". Launch it and type in the search field "Battery".
Click to expand...
Click to collapse
cool, thanks. Let me try this app on my unit for battery setup part
May I know how about the startup part, anyway I can make the app screen do not popup and make a more silent startup?
(for my firmware, I can make app startup automatically in settings -> user -> application settings
Thanks again
@KёniG
I've switched to paid version and turn on "silent start" seems it will just flash then go away which is good now.
However I don't find the way to open the app to change settings anymore (don't see the icon at notification menu) . need to wipe out the app data to get back to setting screen
jasonwong28 said:
May I know how about the startup part
Click to expand...
Click to collapse
My answer above is about silent start up.
If you have the restricted notification bar it is required to reinstall the app to enter settings. Silent mode is not appropriate way for you.
KёniG said:
My answer above is about silent start up.
If you have the restricted notification bar it is required to reinstall the app to enter settings. Silent mode is not appropriate way for you.
Click to expand...
Click to collapse
Thanks, so either I can still choose silent startup but need to reinstall app if i need to change settings
Or
I dont make it silent startup but i will see the setting screen everytime the unit starts?
and one last thing
After I use musicproxy+widgetupdater. When I use my wheel button - "mode" to change the source, it will go through radio, Phone, Bluetooth music, then my specified music player, then stopped if i press "mode" again. Originally, the next app is the map and then loop back to radio. Is it normal behaviour?
Thank you so much
Played a bit more, seems AIMP is working fine to loop the button cycle.
Your problem got solved?
SamWarner01 said:
Your problem got solved?
Click to expand...
Click to collapse
silent startup still make the app no longer configurable but is ok as I don't think need to always configure that often.
For wheel button issue, I find out is my specific app (KKBox) issue. If I change to AIMP or another music app then is working fine to cycle the sources.
And i think a setting which is quite useful for me is "Multiple music app" which will show current playing app info in that widget area