Problems/Questions with the Here App - Samsung Gear S3

Hey guys,
I tried to navigate with the Here app on my s3 classic a few times now. However, it only works when the GPS on my phone is turned on. Is there any way to navigate with the built-in GPS of the watch?
Besides, I have a second problem with the Here App. When I start a navigation on the Smartphone with here, the app also starts on the watch. But instead of starting the navigation, it just shows me my current location. Is this usual?

Yep, would love a single thing;
1. I start navigation on the phone ( A pity that Here does not use my contacts)
2. show the left, right, etc arrow on my gear.
3. Speak te direction.
Thats all
HUIB

Related

[Q] Navigation

Well guys I had bought Samsung Galaxy S Plus yesterday and prior to this I had iPhone 3GS. Since I am new to this phone have a question. While using the navigation (directions) the screen blacks out after the normal time even if I am driving on a car. In iPhone the screen would never go in the power saver mode if I happen to be on the move while using the driving direction in navigation.
Is there a special setting that I need to do.
Thanks
Hi
Any help in this matter would be highly appreciaated.
Thanks
u mean u using google maps? get keepscreen from market. it helps to turn on ur screen until u turn it off
Another think that I noticed is that the screen would not refresh in real time as I drive. A time comes when eventually the My Location moves out of the screen and I have to slide the screen to look for my Current Location in the Navigation.
Thanks
This doesn't seem right. Which app are you using to navigate and in which country are you?
I am in India (Delhi) and am using the Navigation app of Samsung Galaxy S +
sunbaj said:
I am in India (Delhi) and am using the Navigation app of Samsung Galaxy S +
Click to expand...
Click to collapse
Try sygic aura
Sent from my GT-I9000 using XDA Premium App
Thanks
Hi,
Well thanks for mentionong the app .... but it has only 7 day trial and is a costly app .... would cost me 40 Euros....
Well let me elaborate the problem.....
1. I go to google map and then go to maps.
2. Select my start and end destination
3. The direction comes up on the map.
4. There are routes which has turns in short distance for which I have to zoom in else I cannot make out the turns.
5. Now when I zoom in and press the My Position Icon (which is at the right top corner) the zoom gets deactivated and I am back to the point where I cannot make out the turns in the screen as the whole route is compressed in a screen.
6. Also sometimes it so happens that my current location icon (the blue arrow) is not in the screen which is being displayed to me as the screen does not move with the blue icon but at times I am able to do it .....
What I understand is that there are some specific steps which needs to be followed which I am not aware of to activate the functionalities that I am looking above. Can someone direct me to those.
Thanks
Please check this thread.

Watch not turning on from double tap? Also, possiblity to make an app?

Bought this watch today, off Craigslist for $40 in new condition with all original accessories, the white band had actually never even been opened.
Everything seems to work great except double-tapping the screen doesn't turn the watch on. I do have the watch set to that option (First choice, the digital watch-face with the double-tap turn on) and after choosing said watchface, it works fine for a while - but I try again 10 minutes later and it doesn't work. Any idea what might be causing this?
Also, I am loving every feature of the watch except there's one thing - I'm wondering if there's any app or other way to make it so I can hit a button on the watch and have it open S-Voice or Google Now automatically? I think it'd be cool to, as I'm going to bed, be able to hit a button, say "Wake me up at 7" and have it do so (Yes, I know the phone would have to be near by to hear the voice command as the watch has no microphone)
Try double-tapping the bottom left corner - it's more sensitive there. But this "Bluetooth deep sleep" problem, as it is called, is common.
You can also try turning the watch off (long button press) and on again to wake up its Bluetooth.
You can use two finger to hit it. The most sensitive time is when the mn2 turn to the Clock screen and turn off the screen.
The double tap feature only works when your last screen is the clock(either by using two fingers until you go back to the clock screen). You could also doubletap the band instead, since it seems like its the accelerometer that's sensing the "taps"
You can use AppWidget launch apps that use widget, not sure if s voice or Google Now use widget shortcuts, but this should give you an idea.
There's is an app for seach on the play store
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

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

How do you toggle between current app and watch display etc?

Loving my Gear S3 Frontier but still a bit confused about using it on occassions! Can anyone tell me is there a simple way to:
1. Keep an app you are currently using on the display?
For example, while walk around the supermarket, I was using the excellent "My Notes in Gear" to work through a shopping list I'd created previously. Problem was that when the watch display turned off if I raised my wrist up to look at the screen it frequently had reverted to the watch display. Only way i could get it back to my shopping list was to select the apps view and tap on the "My Notes in Gear" app again. Surely I must be doing something wrong and there's an easier way to resume the view of an app you are currently using?
2. Easily toggle between watchface (time) display and current other app in use?
Say I'm tracking a hike in S Health but I want to check the current time. Is there an easy way to toggle from S-Health to the watchface, and then quickly switch back to S-Health tracking again?
Having had the watch a couple of weeks now I'm sure I should have a handle on these things by now, so maybe I'm just being dumb - or maybe these things are not as easy to do as they should be?!
Really, NOBODY has a solution to this??!!
SirBindy said:
It's not rocket science.
Set your double-tap home button to "last app".
Click to expand...
Click to collapse
Thanks for the tip. OK, maybe it's not rocket science but to me it seems very strange that there's is not a standard quick way to click back to a current open app. After all, on your mobile phone it's very easy.
And is there any easy/quick way to toggle between watchface (time) display and current other app in use, as when I just want to quickly check the time? Yes, I realise now I can optionally set my double-tap on the home button to view current app, but what if you prefer to set that to normally open another app like S-Health or S-Voice? Sorry, but I really think this is an aspect of typical use of a smartwatch that the designers have not fully thought through. Surely the ability to easily switch between your watchface and another app you are running should be a standard and quick operation?!
I'm having the same issue. And yes, I've set the home button to revert to my previous apps. I'd prefer, however, to raise my wrist and have the app that I was currently using still be there. For example, whenever I'm out on a run and I'm listening to music, I have to double press the home button, and select the application in order to begin toggling to the next sound track. Similar situation happens when I'm using the notes app. Does anyone know of a way to "lock" the current app so that it doesn't go away when I put my hand down?
Worked in the previous Gear 1&2&S. There are a setting for movement activation : Last screen or Clock. Very usefull, do not know why Samsung removed this setting in the Gear S2/S3 ???
It does this on Galaxy Gear too.
It makes much more sense the app you're using is just there, no need to press any button :-/
Thanks for the double tap tip.

Question Problem with maps+android drive app

Having a problem that while navigating with Google maps on Note 20 phone, watch 4 displays turn-by-turn. When I try to navigate away from the turn-by-turn on the watch 4 (because I'm using maps on the phone while driving with phone in a dock) maps stops navigation on the phone as well. Only thing I can think of is to unpair the watch while navigating but that defeats the purpose of having all the other notifs that I like on the watch and typically forget to re-pair the watch after stopping navigation.
Go to Google Maps on your watch, go to setting, auto-launch and deactivate driving.
fsvancim said:
Go to Google Maps on your watch, go to setting, auto-launch and deactivate driving.
Click to expand...
Click to collapse
Thank you so much. I kept looking through the Maps app on the phone thinking it was something in the phone app since the phone app was the one disconnecting. Also took me forever to even find the settings in the watch app since it's hidden in the "search" menu.

Categories

Resources