Database Info

Google Now Not Listening: US

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

Nexus 5 phone dialer buggy?

Maybe just me but the phone dialer feels buggy. Several times i select a number on the call history list to dial. It seems to then be stucked on dialing. if i hit back and manually dial the same number on the number pad then it dials through. Also does anyone have problem with dialing out or receving phone call, then hang up and music playing doesn't resume? I have this problem with n7player and also somewhat buggy with poweramp..

Still have problem with it and can't figure if there's anything to make it better. I would have poweramp playing music then hit the dialer app. dial a number and as soon as i do that poweramp is shut down. after hanging up music doesn't resume because it appears the music player has been killed. When the music player is restarted, volume is messed up or it sounds garbled. This seems even worse with my stereo BT headset jabra BT3030.
Anyone else got this problem? I mean am i really the only one with this problem?

I do not use the dialer, as I am a teenager so I just text so I can't confirm anything. Haha. Anyways, try ExDialer from the Play Store. You will loose the new 4.4 dialer features like business caller ID, if that matters to you. You can change the theme if you don't like the stock theme.
Sent from my Nexus 5 using Tapatalk

supitsronnie said:
I do not use the dialer, as I am a teenager so I just text so I can't confirm anything. Haha. Anyways, try ExDialer from the Play Store. You will loose the new 4.4 dialer features like business caller ID, if that matters to you. You can change the theme if you don't like the stock theme.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Its a phone so dialer needs to be working as simple as that.... o/w cant call it a phone.... So no one else has any troble with dialer interfering with music app and music resuming playin hanging up?

wildpig1234 said:
Its a phone so dialer needs to be working as simple as that.... o/w cant call it a phone.... So no one else has any troble with dialer interfering with music app and music resuming playin hanging up?
Click to expand...
Click to collapse
The music apps you are using may not be yet compatible with Kitkat. Try testing Google Play Music (comes with phone) and see if the problem persists.
Sent from my Nexus 5 using Tapatalk

supitsronnie said:
The music apps you are using may not be yet compatible with Kitkat. Try testing Google Play Music (comes with phone) and see if the problem persists.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The two i tried are poweramp and n7player. The reasons for those apps? I need a player that has lockscreen control and queing files to a playlist by being able to select files individually from folder view and multiple saved playlists. There are actually not too many of apps that has all those as several does not have folder view of files anymore. Google play music app does not have folder view of files

after MUCH pain i got google music play to work and yes it does work with dialer and pause and resume music properly with phone call. it does have a so and so lock screen control but no adding file to playlist by folder view. what a pain. am i the only one missing the folder view?

wildpig1234 said:
after MUCH pain i got google music play to work and yes it does work with dialer and pause and resume music properly with phone call. it does have a so and so lock screen control but no adding file to playlist by folder view. what a pain. am i the only one missing the folder view?
Click to expand...
Click to collapse
Have you tried Android Music Player from the market? Works fine resuming the music to my Bluetooth after a call

qwerty1gr said:
Have you tried Android Music Player from the market? Works fine resuming the music to my Bluetooth after a call
Click to expand...
Click to collapse
Does it have folder view of files and lockscreen control and multiple playlists?

I have found if you turn off animations "developer mode" it messes with the dialer.

I've found the dialer to be perfect, and so far haven't had a problem with it. I found it SO cool when I called my work number and the name and my logo came up idk if this is just me lol but I thought this was the coolest thing ever.
{
"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 am still trying to decide if it's the dialer problem or if it's the music app problem. Google play music app works fine resuming music after making a phone call. I just wish google music play app has an add file to playlist from a folder view. I am kinda old school....

I've had problems with the dialer itself. Was working fine for me now it freezes. Sometimes I receive a phone call and I cannot answer it. I had my settings set to ART and now I switched back, cleared the cache, and I'm still experiencing problems. I have a custom recovery and am rooted. Not sure if that's the issue but this just recently became a problem. I did have my animations turned off. I'm going to try turning them on as someone suggested. Will report back.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Tried a factory reset and was still having problems with the dialer. Then I went into the mobile data settings and set it to auto roam, I have sprint so I did not select sprint home only. I also set it to accept roaming and kept the network mode to global. I had changed that to LTE before and also have the roaming network set to Sprint only. Now that I changed these settings I can receive calls and sail out without any problems even with my music player on. Hope this helps.
Sent from my Nexus 5 using XDA Premium 4 mobile app

pdubzzle said:
I have found if you turn off animations "developer mode" it messes with the dialer.
Click to expand...
Click to collapse
THANK YOU!
Specifically, it is the "Animator Duration Scale." The other two animation settings can remain off and the dialpad will still appear.
That was bugging the crap out of me.. !

pdubzzle said:
I have found if you turn off animations "developer mode" it messes with the dialer.
Click to expand...
Click to collapse
I had been going crazy over this. Thank you so much for this useful tip! :good:

Korean Firmware update November 20 2015

Well Korea got another firmware update this morning. The update never gave details but here is what I've found so far:
In the settings under Device, there is now an "Auto open apps" option. Basically when you scroll through your apps list, whatever app you stop on will automatically open.
Also in the settings under "connections" there's an alert option now to be notified via vibration when disconnected from your phone.
Under the display setting there's now a screen timeout option. 15 secs, 30 secs, 1 min, or 5 minutes.
Also some bloatware was added. Apps added were a world clock, starbucks, a korean navigation app, and the flipboard news briefing app. There's also a few watchfaces added, nothing new, same ones shown at the initial unveiling. All of them can be uninstalled thankfully.
There's a notification indicator option now also in display. It will make a little orange circle appear on your watchface until you've viewed the notification. Only works if you don't have notifications set to automatically turn on your screen in the Gear Android app.
When reading the text of a notification, it will make the font larger if you double tap the screen.
Cosmetic differences:
now says "add widget" under the + symbol when you scroll all the way right.
On a notification, when you swipe up to dismiss, it now shows a trash can.
For a notification reply, the emoji symbol has been replaced with a more traditional circle happy face.
When you scroll right on the watchfaces menu there's an option to "Add template" now. It then lets you choose from the watchfaces that can be stylized and make a new face from them.
{
"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"
}

Some useful updates, thanks for sharing..
Sent from my SM-G928F using Tapatalk

The screen timeout option was the thing I was waiting for. Good they have it now.

Thx for sharing.
How are the updates rolled out? Seems that austria does not get much love from Sammy...
Is there a way to force the update?
Sent from my SM-G928F using Tapatalk

I'm looking forward to having the "Vibration when disconnected" feature back. Had it with the Gear S

Any update on sleep monitoring?

95SKY said:
Any update on sleep monitoring?
Click to expand...
Click to collapse
I noticed small cosmetic changes inside the S-health app, but nothing else beyond that. I've found nothing related to sleep monitoring.
Also checked yesterday to see if a reminder can be set using S-Voice, and that is also still broken.

I can't believe they didn't map the top button to toggle most recent app... it's so annoying having to go back to the app screen to get to your music app while running... the button is basically wasted without a double click or long press option.
I glad they brought back the vibrate when disconnected function.

Jrsharp70 said:
I can't believe they didn't map the top button to toggle most recent app... it's so annoying having to go back to the app screen to get to your music app while running... the button is basically wasted without a double click or long press option.
I glad they brought back the vibrate when disconnected function.
Click to expand...
Click to collapse
In SHealth I'm able to swipe/twist to the right and get to the music controller, which then returns to SHealth when I press the back button.

Coming from Pebble I expected apps to be persistent and not just to have the watch exit home to the watchface everytime the display times out. It's really nice to have a persistent app for a music player. I could adjust the track or volume without looking at my wrist. And it's also greatly needed for the stopwatch. A settings option for persistent apps would be great.

My Gear app updated this morning, I see no change in the watch. The app on the phone has a whole new layout, but nothing has changed on the watch. Still shows the same J3 software version. I rebooted the watch and nothing. Do I have to reboot my phone? I hate to try this as it always breaks my weather app and I have to totally uninstall all gear apps on the phone and factory reset the watch to get it working again.

becca0327 said:
My Gear app updated this morning, I see no change in the watch. The app on the phone has a whole new layout, but nothing has changed on the watch. Still shows the same J3 software version. I rebooted the watch and nothing. Do I have to reboot my phone? I hate to try this as it always breaks my weather app and I have to totally uninstall all gear apps on the phone and factory reset the watch to get it working again.
Click to expand...
Click to collapse
If it's not a Korean Watch, just be patient. The app was updated, but they have not pushed the new firmware out to the rest of the world. To confirm this, go to Settings->About Gear->Update Gear Software->Update now.

ColMustard said:
If it's not a Korean Watch, just be patient. The app was updated, but they have not pushed the new firmware out to the rest of the world. To confirm this, go to Settings->About Gear->Update Gear Software->Update now.
Click to expand...
Click to collapse
Ah, I understand now. Thanks, got to excited to soon.

display time out
So I got the update on my classic watch, there is 5 new watchfaces.
There is also a new option on the display settings so now you can choose the time from 15 sec up to 5 min.
If i set the display timeout on 5 min it's nothing change...
So I do not understand what the problem is or the new options mean???
Could anyone help me?
Regards
Elvis

You guys are lucky.
In korea some devices that are updated got stuck at booting logo.
I think it will be soon fixed and then you can get this update.

Jrsharp70 said:
I can't believe they didn't map the top button to toggle most recent app... it's so annoying having to go back to the app screen to get to your music app while running... the button is basically wasted without a double click or long press option.
I glad they brought back the vibrate when disconnected function.
Click to expand...
Click to collapse
I agree there should be a long press top button feature. The way I deal with this problem is I set long press home to the music player. Then to access apps you press home then press home again.

Encrypted Phone
So I have the Nexus 5X, aka phone is encrypted.
My watch is from Korea and the app does have an update, but I get the error message that it cannot install because phone is encrypted. Any solutions?

My Gear Fit, which isn't actually Tizen, but resembles it a bit, has an option for what you want to do after timeout - return to watch face, or remain on last app. Very handy, and Samsung could certainly add this option, since they already know how it works.

FitzAusTex said:
My Gear Fit, which isn't actually Tizen, but resembles it a bit, has an option for what you want to do after timeout - return to watch face, or remain on last app. Very handy, and Samsung could certainly add this option, since they already know how it works.
Click to expand...
Click to collapse
I really want that option.

Some decent additions there, but I was really hoping Sleep Tracking would be included.
Sent from my SM-G900I using Tapatalk

Turns screen off, podcast quits

Topic pretty much tells my problem. Even though I have made sure that battery optimization is off, any podcast I play will stops when the screen goes off.
I've tried 3 different apps.
Any suggestions?

Try This
Had same problem. Try going to Settings/Other/Close Apps After Screen lock and ensure whatever podcast app(s) you're using are not selected to close when screen locked. Also when podcast is playing, hit recent/overview apps button on nav bar. There will be a padlock icon on upper-right of card of podcast app. Make sure it looks like a locked padlock instead of an unlocked one by pressing it until it looks locked.
Even with above fixes I still get shutoffs when using navigation and playing podcast at same time, i.e., when I turn navigation off, podcast will turn off when screen locks. I simply wake screen and start playing podcast again, and then no more shutoffs (until I use navi again as described).

jrotert said:
Had same problem. Try going to Settings/Other/Close Apps After Screen lock and ensure whatever podcast app(s) you're using are not selected to close when screen locked. Also when podcast is playing, hit recent/overview apps button on nav bar. There will be a padlock icon on upper-right of card of podcast app. Make sure it looks like a locked padlock instead of an unlocked one by pressing it until it looks locked.
Even with above fixes I still get shutoffs when using navigation and playing podcast at same time, i.e., when I turn navigation off, podcast will turn off when screen locks. I simply wake screen and start playing podcast again, and then no more shutoffs (until I use navi again as described).
Click to expand...
Click to collapse
Thanks for the suggestion. But that is the setting I was referring to by saying 'Battery optimization' setting done. The actual menu path to that is Settings/Battery/Close Apps After Screenlock. Another interesting thing: I do NOT see an Other option in Settings. BUT...when I search for Close, it then shows up as a category of Other, which then when I click on it it takes me to the Battery area, and then I can click on Close Apps AFter screenlock.
Anyway I do have to set correct.
But, I just now checked, and the padlock you refer to is unlocked. So I just changed that. I have not noticed that before, and have no idea what it really means. I presume it means to not close it. ... Just clicked on the trash can in the nav bar, and it did NOT close the app. I bet I'm good to go now.
I'll report back on my success with that.

Like you I see improvements, but not a fix.
I am constantly having issues like this (by like this I mean things that should just work) on my Android phones. Never had one that didn't have some type of frustration.
Makes me wonder if it's any battery on an Apple. I'd hate to lose the flexibility. But I read an article recently that says IOS statistically had more failures than Android. I have no idea if that's true.

Trying to figure this out with my s22

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Featured by:
XDA-Developers: Customize the Google Pixel 2’s Active Edge to do any action with Edge Sense Plus [XDA Spotlight]​
What is Edge Sense Plus?
Edge Sense Plus was initially just meant for the HTC U series. It let's you customize the squeeze action and adds some more squeeze gestures and features.
But with the Pixel2 also coming with a squeezable frame I had the goal to make it compatible with it too.
..and after a couple of days debugging with @k4r70ng (I don't own the device, big thanks to him, was a great help) we are here now!
Requirements
You have to be on Oreo 8.1 or Android P.
You need to run a STOCK based ROM, because Active Edge is broken on AOSP roms.
You need to be rooted with magisk to use it.
Install the Active Edge System Mod Magisk Module from the MagiskManager Repo and the EdgeSensePlus from the playstore and you are ready to go!
Telegram Group
Join Telegram Edge Sense Plus Group
How does it work
To make it working on the Pixel2 I had to modify the SystemUIGoogle.apk that runs the ElmyraService (Service that processes the squeeze gestures).
I intercept the events and pass them to the EdgeSensePlus Application that starts the appropriate action then that you selected.
Some more adjustments were made, so the squeezing also works when you are in immersive mode, camera or when Google Assistant is deactivated/uninstalled.

What can it do?
Custom actions:
Currently you can choose from over different actions
Quickly Start camera - Also when screen is off and locked
Per App Action - Execute different squeeze actions depending in what app you are!
Sidebar
Gesture Panel - Draw custom gestures to start different actions
Custom App
Shortcuts - e.g. to make direct calls, start tasker tasks and more!
Scroll up/down
Flashlight
Recent Apps
Toggle Autorotation
Autobrightness (6 states: Auto, Min, Low, Mid, High, Max)
Split Screen
Expand/Collapse Statusbar
Toggle NFC
Toggle Display on/off
Toggle Autorotation
Toggle DND
Toggle Vibration
Toggle Bluetooth
Toggle WiFi
Music Play/Pause
Previous Track
Next Track
Toggle Keep awake
Google Assistent
Lock Screen
Back
Home
Toggle Sync
Sync all accounts
Previous App
Take Screenshot
Clear all notifications
GPS
Answer/End call
Immersive Mode
Shell command
Per app actions:
With the per app action, you can define different squeeze actions per app. So the chosen action will be executed dependent in what app you are currently are.
Double Squeeze: (Premium)
If you often accidentally trigger a short squeeze, that won't happen anymore if you map your desired action to the double squeeze gesture.
You can define a double squeeze interval, to ensure you are quick enough to trigger it every time.
Long Squeeze:
Missed a long squeeze action on your Pixel? Edge Sense Plus has it!
G-Sensor usage: (Premium)
If enabled, will be able to execute different actions depending on the current position of your device, whether it is flat or upright in your hand.
That way you can have six different squeeze gestures: short, long, doublepress in flat or upright device position.
Media control:
The media control will override your set squeeze actions while media is playing so you can control your media.
That includes play/pause, increase/decrease volume and skip to next and previous track.
Squeeze sounds:
Ever thought it would be funny if a squeeze of your Pixel2 would make a sound, if it is a *click*, *oink* , *fart* or whatever you think of?
You can use any .mp3 file to make that happen!
Sidebar:
The Sidebar has 4 different panels, Applications, Shortcuts, Recent Apps (Premium), Quicksettings (Premium).
Panel colors are customizable

Instructions
You must be on at least Oreo 8.1 to to be able to use it. Root with Magisk is required since the magisk module is mandatory!
It is recommended to have a working TWRP backup in case something goes wrong. Check the FAQ for help too.
Like always: Flash on your own risk. I'm not responsible for any damaga to your device
Flash the Magisk Module either in Magisk Manager or TWRP
Install Edge Sense Plus
Enjoy.
Downloads
Now also available via the MagiskManager Repo:
I recommend to install and update the Magisk Module directly via the MagiskManager repository directly in the MagiskManager app.
All releases will be also available on the GitHub repository
Edge Sense Plus:

Ok lol I am blind, thanks for app!

This looks great and more powerful than other options to intercept the squeeze gesture. Thanks for taking the time to port it!

Would it be possible to provide a module download with an Md5? I downloaded and flashed the module, wound up in a bootloop and had to restore a backup. I'd like to try this, but really want to be careful. Thanks

FAQ
Q: Will it also work on the Pixel2 XL?
A: No, it will bootloop your device. There is a separate thread on the Pixel2 XL forum.
Q: My device bootloops after flashing the magisk module.
A: Ensure you are on the latest Pixel2 OTA. To get out of the bootloop, go to the magisk thread and install the magisk uninstaller and then reinstall magisk again.
Q: The magisk module zip is greyed out when I try to install it.
A: I have no explanation why it happens for some. Install a FileManager like SolidExplorer or FX File Explorer, then Select that File Browser in the System File Explorer to select the path

Thanks. Yeah Pixel 2 on the latest January update with TWRP and Magisk 15.2.

Yep it was a bad download. Thanks for the Md5. I'm all set now :good:

jascolli said:
Yep it was a bad download. Thanks for the Md5. I'm all set now :good:
Click to expand...
Click to collapse
great, glad to hear.

Love the app so far! One thing that bothers me is that when I launch google assistant, it makes the beeping noise twice. Is there anyway to change that?

SuperSmashedBro said:
Love the app so far! One thing that bothers me is that when I launch google assistant, it makes the beeping noise twice. Is there anyway to change that?
Click to expand...
Click to collapse
Aware of that. Will look into this today. Does not happen on my U11... so debugging will take a bit longer.

Are there any plans to distribute the app through the Play Store? And is it normal for the app to constantly ask me to upgrade to premium? By constantly, I literally mean constantly. It seems to be tied to scrolling down the settings page, and it pops up 2-3 times before I reach the bottom.
Also, will squeezing still silence an incoming call? Are there any settings that might prevent the squeeze from silencing an incoming call?

AZImmortal said:
Are there any plans to distribute the app through the Play Store? And is it normal for the app to constantly ask me to upgrade to premium? By constantly, I literally mean constantly. It seems to be tied to scrolling down the settings page, and it pops up 2-3 times before I reach the bottom.
Also, will squeezing still silence an incoming call? Are there any settings that might prevent the squeeze from silencing an incoming call?
Click to expand...
Click to collapse
Currently the app is just visibible for HTC U Devices.
Im afraid of bad ratings from pixel users, since it does just work with root. On the U11 it works without.
Will try improve the scrolling issue.
I just override the google assistant action. So the other native squeeze actions should still work.

AZImmortal said:
Are there any plans to distribute the app through the Play Store? And is it normal for the app to constantly ask me to upgrade to premium? By constantly, I literally mean constantly. It seems to be tied to scrolling down the settings page, and it pops up 2-3 times before I reach the bottom.
Also, will squeezing still silence an incoming call? Are there any settings that might prevent the squeeze from silencing an incoming call?
Click to expand...
Click to collapse
Can you check if that fixes the scrolling issue?
https://www.dropbox.com/s/1rs8vn24o27vrxb/app-release.apk?dl=0

j to the 4n said:
Can you check if that fixes the scrolling issue?
https://www.dropbox.com/s/1rs8vn24o27vrxb/app-release.apk?dl=0
Click to expand...
Click to collapse
Your update seems to have fixed the constant update pop-up for me. Thanks! Just bought pro for the additional features. Awesome work!
Sent from my Pixel 2 using Tapatalk

btreu1 said:
Your update seems to have fixed the constant update pop-up for me. Thanks! Just bought pro for the additional features. Awesome work!
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Much appreciated (-:

I've noticed that pocket detection makes active edge misbehave. I don't know if this is a known issue, but I thought I'd share my experience.
The other thing I thought was an issue was with setting a shortcut to a Tasker task. For anyone who may not understand how it works, you have to open Tasker and choose "exit" from the menu at the top right of the app before you can set the task shortcut in Edge Sense Plus.
Sent from my Pixel 2 using Tapatalk

btreu1 said:
I've noticed that pocket detection makes active edge misbehave. I don't know if this is a known issue, but I thought I'd share my experience.
The other thing I thought was an issue was with setting a shortcut to a Tasker task. For anyone who may not understand how it works, you have to open Tasker and choose "exit" from the menu at the top right of the app before you can set the task shortcut in Edge Sense Plus.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
In what way misbehave? No issues reported yet on the u11 for half a year

Playstore compatibility for Pixel2/XL
burp